Archive | Professional Development RSS feed for this section

OpenMRS – Night 1 of Many

21 Nov

I’m currently at an OpenMRS hack night – the first of many such nights that I intend to be part of. I’m coming up to speed with the cause, and the module we’re working on. It’s pretty interesting work, and I’m thrilled to be part of it.

What I’m not so thrilled about is the turn out. That’s why I want to see YOU there! Come on!

Here’s the deets for the Melbourne & Sydney hack nights:

This slideshow requires JavaScript.


If you’re interested in coming, and want to know how you can help out – just let me know!

Ruby Newbie

5 Sep

Wow, just wow. I know this book is educational, I know it’s about coding and I know I have other things to do right now; I only took a look because I was curious but wow, oh wow, I cannot put it down. I want to keep reading, god forbid I want to learn!, and I just can’t tear myself away. I’m pretty sure I won’t sleep tonight.


Now you’re curious too. I know you are. Go on, go learn ruby.


//Here’s hoping for a promotional cut of why‘s highly dreamed of earnings. And yes, I see the flaws in this plan.

Retrospective Sandwich

19 Aug

In the middle of running a retrospective, just the other day, I realised that the somewhat standard focus of “what went well; what didn’t; what can we do better” is effectively an adapted feedback sandwich.

The feedback sandwich is, at best, a guide on how to give another person feedback in a less hurtful or confronting manner. It’s really easy to put together. The recipe features: 2 Positive Comments in place of bread slices; 1 constructive comment in place of salads and cured meats (is anyone else hungry just now?).

By starting and finishing on a positive note, the feedback is meant to not only be easier to deliver, but also more appetising for the receiver to take action on later. In this same way, the “what went well” and the “what can we do better” can be seen as a different variation of the positive bread slices, whilst the “what didn’t” focuses more on the meatier part of team development.

Puns aside, having realised this, I am aware that there is more room to create energising, or even inspiring, team retrospectives. Time to cook up a little something for the next one 😉

Kanban Love!

4 Jul

I love using Kanban. It’s great for tracking non-project or repetitive tasks – like housework. It’s a great way of communicating with others – when the Kanban wall is up, my partner doesn’t miss the fact that the floor needs mopping or the laundry needs washing. Placed centrally, it’s a great visual reminder – I don’t need to nag!!!

Whilst I like using it at home, it’s also a great fit for the workplace.

Want to find out more? Great! Just ask me sometime!

The Next Steps (my learning journey)

23 Jun

After the strong finish point of my previous post, the youngest voice in the room, I’ve decided to look for inspiration on how to take those next steps. I recently picked up a copy of The Passionate Programmer, and whilst I am not a software developer, I find it still has plenty to offer in supporting my journey.
The text had me in its grips from the foreword, and just kept drawing me in. One of the key points made is that “a person who wants to become great is far more likely to be great” – that to treat your job just as a job is unlikely to lead to happiness, let alone success. The passion that comes with wanting “to be great” subsequently offers a lot of drive and energy for achieving just that.
Whilst I do recommend reading the book if you have the opportunity, I would briefly like to share just three of its tips that have resonated well with me:
  • Find a mentor
    Whilst there are many opportunities for self-driven learning (i.e. endless reading, attending events, and so on), experience has taught me that without someone else to bounce ideas off, I have no idea what I’m missing out on.
    Let me explain this another way: The way we think has often been described to me as drawing from four aspects of our knowledge – (1) what we know that we know, (2) what we don’t know that we know, (3) what we know that we don’t know  and (4) what we don’t know that we don’t know. — At this point in time, I am unsure of where this concept first originated, and hence who to attribute it to.
    1. Obviously the first, what we know that we know, is knowledge that we apply when we can. For example, I know that mingle is a pretty useful tool, and I know how to use it. I use this knowledge daily.
    2. When I don’t know that I know something, it often comes as a surprise – information that is stored in the back of my mind, that I absorbed at some point and have retained, that jumps to consciousness when I need it. For me, this is primarily medical information, as when I was younger I entertained a love of biology books and, a few years after that, would often help family and friends study for medical/biology courses. Right now, whilst writing this blog, nothing related to medicine/biology comes to mind, mostly just vague ideas, but I know from experience that if somebody were to ask me about, oh, what ibuprofen is or what interacts with calcium supplements, or maybe even about kidney diseases, I would probably pull the answer an accurate, informed answer from the depths of my memory, and each time it would surprise me, yet I would know it to be right.
    3. When I know that I don’t know something, I can seek out the information myself. This is when reading and self-learning is most useful. For example, at the start of this year, I did not know what mingle was, and at some point I knew that. It was then that I looked it up on the internet (like you likely will too – go on, click the link!), found out more about it, and trialled the software.
    4. The problem with the above example though, is that I first needed someone to tell me of something new, for me to know that I didn’t know about it. There are endless collections of thoughts, facts, ideas and knowledge that I cannot even fathom – to learn more about them, first I need some inkling that they exist. For example, I bet you didn’t know that you didn’t know about this concept. And now you’ve gone from (4) to (3) knowing you didn’t know to (1) reading about it here and now knowing that you know. This is where you most need triggers for your curiosity, and where a mentor can help out most.
  • Practice 🙂
    Not by doing what is comfortable, but by stretching your limits and trying new things. This may mean presenting at a conference, when you’ve only ever presented to your university class. Just go do it, and treat it is a learning challenge.
  • Learn to fail
    It’s not really about failing, but about being okay with potential failure. If we don’t feel capable of coping with it, chances are we won’t try in the first place. Recently, I was organising a vacation trip through the North of India, but I wanted it to be perfect. Knowing that I did not know enough to make it perfect, and knowing that I was certain to fail in actualising my feeble plans, I hesitated, and hesitated again, and kept postponing the bookings. Finally, a month before I was intending to travel, after realising I was going nowhere, I contacted a local travel agency, in the hopes that they could help me. I was relying on their expertise to prevent certain failure. When I ceased getting timely responses from them, I just waited. Knowing that something had gone wrong, I did not want to follow up with them and get the bad news, I preferred to hope it would turn out all right. In the end, things had gone wrong, and my entire vacation had to be replanned, but I only came to grips with this the day before I was due to fly out.
    Failure has its benefits – the primary one being that failure is often a learning experience.
    Additionally, failure is not as scary as we often make it out to be. The damage of my failed trip planning was little – it just required some replanning. This occurred much later in the process, but could just have easily been tackled months earlier. The damage caused by my lateness in facing the failure – major out of pocket expenses, due to the lateness of rebooking.


The youngest voice in the room

9 Jun

I was recently invited to partake in a 3-day strategy meeting, to assess and make recommendations for the future of our graduate program. That’s pretty exciting for me, because the graduate experience is something I feel quite passionately about. Then my eyes were drawn more closely to the words “strategy meeting”. I took a look at the names of the other invites, and saw People Leads and Recruiters, and well known employees and old-timers. What then, was my reaction?
“Uh-oh, looks like I’ve been invited by mistake, I should let them know to amend the invite”.
So I went from being exciting and thinking “this is exactly the event I want to be part of”, to assuming it’s a mistake and I won’t belong.
How did that happen?
It wasn’t that I didn’t feel comfortable with the idea, or that I wasn’t competent enough to go, and I definitely wanted to be a part of it. Yet there was an element of surprise: Why would an employee as new or as young as myself be requested to aid in strategy development?
Upon arriving on the first day of the meeting, I found myself confronted again. A colleague even asked “what are you doing here?”. The question was intended to uncover what perspective I, and other attendees, was providing, but I found it a little unnerving. I ran a mental check:
What was I doing here? Do I need to justify my presence? Will I be listened to?
I had a valid view to represent. As a recent graduate, a recent student, my views and my buy in would be just as important as any other.
Not only that, but I could offer the infamous fresh perspective. As a recently new hire, I had lesser view of what had been done in the past, and so less temptation to grasp onto the familiar. I also had a range of other experiences to draw from, that allowed me to offer unique insights. My presence had value. My presence had reason.
This leads me to wonder – are the opinions of the fresh faces being sought out often enough? Or should we continue to lean towards the veterans?
Yet more importantly, how often do new joinees avoid getting involved, because they feel their insight won’t matter?
At present, I only have anecdotal evidence – having been an intern twice, and now a graduate, and having worked and trained with other new joinees, I understand that we often feel we don’t know enough to start voicing our opinions. It’s best to sit back and learn from the experts, that’s what they’re there for, right?
I say that’s not good enough.
No matter what our experience levels, we have something to share, and plenty to learn.
If I’m not confident enough to share my own view, I’ll learn by questioning others’.
My plan is to get more involved in SIGs, giving presentations, or running workshops, if only to raise more questions.
My plan is to not run away.
My plan is to share my perspective.
What’s yours?

What’s your principle?

12 May

I came across this brilliant talk by Brett Victor via Vinod’s blog and, like Vinod, I waited about a month to watch it. There were always to reasons to put it off, the primary one being that it’s just under an hour long, and I needed to find enough time to first stream it, and then watch it. Finally, after going back through my archaic list of things to do, I saw this and thought “ah, what the hell, I’ll never get it off my list if I don’t give it a go.” My one advice after watching it? Watch it. Watch it now. It’s amazingly worth it.

The talk touches on a range of principles, including but not limited to software development, engineering, artistic and problem solving. More than that though, it’s focuses on finding the right principle to guide your life.

So what’s your principle? More importantly (to me), what’s mine?

When I look back on all I’ve done, the roles I’ve played in life, and the driving factors of my decisions, my initial reaction is to say “oh, well I must like to solve problems”. Then I think of how I’ve never actually solved a rubiks cube – I’ve definitely tried, and I know there are plenty of sources to help me understand how to do it, but I tend to just give up instead. It just doesn’t interest me.
“Oh, so maybe it’s because it’s been solved before, maybe I like to solve new problems?”. Then again, I do find important lessons in reinventing the wheel – I think it’s cool to be able to understand something, and then share it with other people.
“Ahh, people! I’ve always loved working with people but … only those who are open to learning”. Yes, I think now I’m onto something. I think my principle is to enable others to grow their own ideas. I’m not focused just on helping others learn, not really. What I am interested in helping people question themselves, their ideas, and inspire them to develop those ideas further.

So now that I’ve reflected on that, I think it’s safe to say that hearing about your principle is more important (to me), after all.