I'm a Software Delivery Consultant who helps CIOs, Heads of Development and Development Managers build and retain happy, productive development teams by modernising their delivery practices.
It's lovely when you log in to the Azure portal, click a button and things magically happen. It's lovelier when you can do the exact same things with an ARM template. It's not so lovely when you stumble across a configuration that isn't actually a single resource, but a collection
I've spoken before about struggles with procrastination, and how striving for perfection often leads to paralysis and inaction. This struggle was all the more pronounced during my stint in tech recruiting - what I didn't realise before I started: recruiting is in some ways very much like sales. The thought
When I first started as a professional software developer, I was far from professional. There's a stack of concepts and approaches that weren't taught when I was at Uni, but were actually critical to being able to do my day-to-day job well. The current proliferation of "learn to code from
Source control is one of those things that's taken for granted in a lot of software teams these days. For many devs now, it's always been there and is just part of the fabric of how development is done. But this wasn't always the case. Many who've been around the
As a developer, how do you see yourself? What is your role in your team, in your organisation? Are you a specialist and a partner, or a code-producer and outsource-able commodity? Many organisations treat software development as a commodity. These are the ones that have been failing at waterfall projects