Archive for the ‘People’ category

Open Sauce

October 9th, 2009

Time Management, an ugly phrase that we all know just doesn’t apply to us, right?  But what about when you’re buried in some complicated ETL, trying to design a new killer dimensional model or wrapping your head around how to implement a Kimball bridge table.  You get a bit stuck and then your mind wanders, you check your email, send an IM, chat to your co-workers, think about getting a coffee etc etc.  If you really never do that then stop reading now (but why are you reading this?).

Thought so.  You need The Pomodoro Technique.

pomodoro

Like all good things, this one is founded on a really simple concept.  Just focus on something, above all other activity, for just 25 minutes.  Then have a 5 minute break.  That’s a pomodoro.  Then repeat x 4, then have a longer break.

Try it. It’s surprisingly difficult for a lot of people, it seems that we tend to operate in an environment with a lot of interruption and distraction.  Francesco Cirillo worked this all out at university in the 1980’s and came up with a method of improving concentration and motivation which seems to have gained a huge following just recently.  I’m interested because it sits well with Agile and Scrum and BI/DW development (time-boxing and and the productive work/play dynamic).  If you read all the documentation you’ll be doing better than me but Cirillo would appear to have seriously researched this stuff.

The ‘internal interruptions’ are the thing that I probably suffer from most - it is actually quite comical when you think about it.  Why all of a sudden, at a particular moment you just have to look something up on the Internet, or make a phone call, or send a text message?

The solution to this procrastination issue, and one of the main benefits of Scrum are the same.  Make the issue transparent.  Just as you would identify and mark an impediment or a newly-emerged requirement as a backlog item in Scrum, so you highlight the existence of the interruption or the pressing need using the Pomodoro Technique.  I think the underlying message is the same - we operate in a dynamic environment so lets recognise and accept that but not let that unduly influence our progress or our short-term plans and goals.  Just as a Scrum sprint is short, so is a Pomodoro.  Lots of short iterations = higher chance of successful delivery which in turn increases satisfaction, motivation and belief.

We do actually have one of those pomodoro kitchen timers in the office now.  Its pretty noisy but probably preferable to an electronic screen-based timer in terms of impact and gained respect.  If you just can’t stand the idea, or can’t find anywhere to buy one (try eBay) then you can download all kinds of timers online, some specifically aimed at this technique, but give it a go, you might be surprised what you discover.

Obama on Education

September 9th, 2009

US President Obama’s speech on Education seemed like a prime candidate for a Wordle.  You can see the entire transcript here and watch a video of it here, but I think the image below also conveys the content well.  This happens to contain the top 400 words and common English words have been removed.

Obama Wordle

I like this speech, its inspiring and motivating and good wholesome stuff that no one can really argue with, nothing wrong with that in my mind.  The biggest word for me - responsibility - of the personal kind.  Education says Obama, is your responsibility.

Shooting Tall Poppies

April 23rd, 2009

tall-poppiesWe live in a curious world don’t we?  You may have noticed an RSS feed over there on the right and down a bit to Flowing Data, a really wonderful and inspiring insight into contemporary data analysis.  The author of this site, who posts some fantastic visualisations on a very frequent basis, has come in for some flak just recently.

You can read a bit more about it here if you’re interested.

Fortunately, Nathan has lots of allies and lots of great messages of support have come his way in the last couple of days as a result.  All I can add to the conversation is that his site, and indeed many others that promote alternate visualisations, provide inspiration and relief to people like me who work in the constrained business world of column and line charts.  Occasionally having read one of his posts I break free and try something radical, and encourage others to do the same.

So please keep doing what you’re doing Nathan, and take the remarks as a compliment, the old guard is threatened - the chart is dead, long live the chart.

Protracting Peers

April 19th, 2009

protractor

Remember these things from school?

Good for measuring angles, and indeed reminding ourselves that there are always other angles or perspectives on everything we do.

I was browsing a colleagues’ blog last week and found an interesting entry that points to a post in the blog of Ben Collins-Sussman.

The post is about the insecurity of IT ‘nerds’ with respect to their work, specifically the ‘develop in a vacuum‘ mentality and the abhorrence expressed at the idea of peer review.  It was written almost a year ago but people are still adding to the debate today and the point is most definitely still valid, very valid, and not just within the sphere of IT.

Our very own DVC, Professor Graham Webb blogged about academic standards in general terms last week and made the point that peer review has an important role to play here too.  I’m not implying that academics or we IT nerds are more insecure than anyone else, in fact I think it is a human trait that we can all improve on.

You can read Ben’s post in its entirety, complete with the subsquent 90+ comments here, but for me, the closing paragraph says it all.

Be transparent. Share your work constantly. Solicit feedback. Appreciate critiques. Let other people point out your mistakes. You are not your code. Do not be afraid of day-to-day failures — learn from them. (As they say at Google, “don’t run from failure — fail often, fail quickly, and learn.”) Cherish your history, both the successes and mistakes. All of these behaviors are the way to get better at programming. If you don’t follow them, you’re cheating your own personal development.

Of course Agile helps us come out of our boxes a little bit and encourages the team approach to planning and execution and I think with that, the team responsibility for failure and subsequent improvement.  It is probably worth remembering that actually soliciting critique is healthy and (aside from ultimately improving the end result) if you are concerned about shouldering responsibility for everything, it provides another pair of shoulders, free of charge.

So Long (Project BI) and Thanks for All the Fish

December 4th, 2008

I am in the midst of converting BI from ‘perennial project’ to ‘core business’ which after 3+ years is significant for UNE. It means that BI has come of age, it is recognised as something that truly gives value to the institution and will continue to do so indefinitely. It also means that the people responsible for BI at UNE have done a great job and should be recognised for that.

So although you’ve moved on to bigger and much better things Norm, a huge thank you to you for getting through those early days with me when we didn’t really know what the hell we were doing, and then to Coops who has learned at an alarming rate, hung in for the last 2 years and really helped us mature the platform and deliver some great technical content, and now to Jing who has taken on the mantle of Metrics and is our resident Scorecard Queen.

And to everyone else who supported us along the way to becoming grown-ups. Thanks, you know who you are.