Time-frames and Velocity

Next Monday I have a meeting with my team lead at 2:30pm. It’ll be the 3-month review mark in my new job, which still feels insane to me.

I blame the velocity of the release cycle at Campaign Monitor. I came from an organisation where releases are carefully planned and executed around a 6-month release cycle to co├Ârdinate deployments with numerous external parties each with their own IT department. I came from an organisation that rightfully was cautious about the idea of Agile and where it might apply. And I’ve jumped straight into the middle of an Agile maelstr├Âm.

We have a release window every fortnight (or more… sometimes weekly). Sometimes that’s just an internal deployment. Sometimes that’s a production deployment with functionality still turned off by default. But it is a deployment. An opportunity for code to be exercised, reviewed in the wild, and feedback to come back. It leads to a much more experimental approach, and a preparedness to be wrong because at worst it will get fixed in another fortnight.

Which makes this morning all the more dazzling in its sudden slow-ness.

There is an issue in some of the development environments. And I’m sure it’ll be fixed by lunch, but in the face of the otherwise blistering speed, half a day without access suddenly feels like the Biggest Tragedy in the History of the Universe.

So in my helplessness I am studying on Pluralsight.

I should post about Pluralsight, because it is more awesome than I ever suspected. In the past month I have completed 30 courses on a variety of topics. It’s the quickest way to get into a new unfamiliar technology for me, and I feel so much smarter already. Just wait until I finish the full catalogue… only 3970 more to go!

Back to Angular.js for me now.

And then lunch with some ex-colleagues. Yes, I am abandoning the chefs. “Chicken and sweetcorn soup” the internal menu proclaims. I’ll be back in time for cookies though.