I’ve traveled for work a fair bit over the past three months – my job has seen me ending up in New Zealand (Auckland & Gisbourne), Scotland (Thurso, via Edinburgh, and then back to London for 2 days off) and in Sydney for a week around Dee Why. While I’ve been away for work I was hoping for some time to multitask – while my main requirement on site has been satisfied (i.e. everything is running smoothly, as expected etc) I had expected to be able to work on other projects, perhaps one specific project which is a little over-due.
Unfortunately this wasn’t how it played out…
I suppose our best laid plans don’t always happen as we expect them to, and in my case it was no different. However part of this was myself allowing minor hurdles stopping me from doing the work I had originally intended to do.
A bit of background
Let me paint the picture for you a bit – I am, as my main vocation, a software developer. Currently I work full-time for a company based in Sydney, but from my cosy apartment in Canberra. This company is based deeply in the surfing industry, and as a result we’re somewhat in events that pop up, mainly within the broadcasting side of things.
Remembering what I do daily – my position in these events is the broadcast technician – at the end of the day a fancy pants word for:
- Setting up the webcast encoder
- Setting up the webcast internet connection (and this varies from ADSL connections, 3G connections, a satellite connection – whatever it is, its my domain)
- Setting up the audio mixer and tuning the levels on the Microphones and other inputs
- Setting up the production mixing desk, video playout system, camera sources etc
- Making sure everything plays nicely together
- Ensuring those who need it can get access to the internet (this, believe me, is a huge problem up in Thurso…)
- then when all that is up and running and no one is panicking… panicking over the things which need to be fixed and educating the runners
- when required, be a runner – at a last resort
I’m not complaining about this though – working on the events is such an amazing experience. Normally I am not a morning person but when you get into these things where you’re up at 5am, finishing off at 9pm, rinse and repeat… its challenging but amazing.
But…
My expectations on how often I would be required, interrupted, etc – completely underestimated. Here I was imagining that I would get everything up and running, then be able to sit down and bash out some code until the next situation – and perhaps I could have.
Unfortunately I fell into the trap of laziness and things would pop up which I allowed to make it ‘hard’ to work on things. And these weren’t necessarily small things either – something like “oh the internet connection is unstable, so I can’t drop stories into Pivotal” or “I am not able to find a comfortable place where I won’t be interrupted, so….”. In hindsight its relatively pathetic.
The moral?
I’m (hopefully) not just blubbering uselessly about my trials and tribulations, I promise – there is a ‘moral to this story’. Recently I sat down with a business partner and discussed how I “didn’t have time to work on this project” – which was not only disappointing to my business partner, because he’s depending on me to deliver something, but it was also disappointing to me, because I was letting my friend down.
During our discussion we decided to setup a bit of a mind trick to get some work churned out. Originally I would say something like “Oh let me work on this tonight and I’ll come back to you in a day or two with it…” and lo and behold, I never delivered… When I was looking back on some things I had read by the guys at 37signals (in their book Getting Real – not an affiliate link, but the book, it rocks!) I remembered what DHH had said about his limited time while working on Basecamp – 10 hours per week, plus there was a time difference from the office being in Chicago and DHH being in Denmark.
With this in mind I decided to try something out – I had already had good experience working in sprints of 25 to 30 minutes, then taking a break, then starting again, so with my business partner we agreed to try something similar. Each day, for 1 hour, we sit down together and bash out some work. It doesn’t have to be perfect, in reality it could change the very next day, but the main thing is that we were making progress – taking that step forward required to gain momentum.
Has it worked?
So far, yes. There have been days, due to appointments etc, where we haven’t been able to meet as agreed, however most of the time we accomplish what we have aimed for and the progress is a good feeling. I still have issues with the procrastination bug at times, but at the end of the day there really is a reason why we procrastinate.
Looking back at the times I was away I could have easily done the ‘work’ I had intended to do while I was away. The reasons seem pitiful:
- I can’t get a stable internet connection – just pick something to work on and churn out some code. If it isn’t right you can go and change it later but at least you have a baseline to work on – a clean slate is just intimidating and makes the problem worse.
- There is nowhere comfortable to sit – Screw comfort – work until your butt goes numb, then take a break – or, perhaps find somewhere to sit down – there were heaps of cars around, even chairs – I’m sure you could have borrowed one.
- If I sit in the car the satellite will lose its alignment – (This one is quite pathetic) The satellite’s by your computer, so it in the car, check the signal strength, and adjust the elevation for the difference your weight in the car makes.
I really wish I could go back and change them. I think that the reason I was procrastinating on this stuff is that I saw it as such as massive task at hand and couldn’t even get the momentum to break it up into smaller chunks, and see each iteration worked as an achievement, but now things are looking a bit different.
So next time you’re stuck perhaps try to keep this in mind. Any momentum is good momentum, and try not to get stuck looking at the big picture. If you are a software developer there is always going to be things you are going to have to look at, review and change, later in the future – so stop being such a perfectionist and just do the damn work.