Software is drowning the world
One of the many upsides I’ve had from working at lots of organisations is that you get to see what’s common. Are things like this everywhere? Frequently, the answer is yes!
Hello, is this thing on?
Intermittent cake-hole flappings of a nerd
Latest posts
Organisation Cultures
If you’ve been here before, you might want to skip to the stories.
Difficult conversations
This is part of the Organisation Cultures series.
Working where you’re not wanted
This is part of the Organisation Cultures series.
Open letter to a Google recruiter
This was a hard email to write, and I’m republishing it here since I think it’s an important issue.
On making active technology choices
This post was originally written as part of the styleguides repository for Marks and Spencer Digital. That repository has since been removed from the internet, which is a very separate, sad tale. The post was needed to prevent technology choices being imposed on teams by The Architects, whilst at the same time ensuring the technology estate didn’t become an uncontrolled sprawling garden.
Assessing coding tests
A bit of internet that I can point to when I have a conversation with people about coding tests.
Devops Defined
It’s 2017 and we’re still having this discussion? Alright then, here are some definitions for your consideration…
Distributed Array of Commodity Hosting Services (DACHS)
not [suitable for] enterprise production use where an enterprise such as ourselves would want an SLA. – anonymous Architect
Types of Engineer
Software engineering is a broad field, with many different specialisms. I tend to consider 4 distinct roles. None of these roles are more senior than another. These are explicitly specialisms, not a hierarchy. There is no right way to be an engineer. You can be one or more of these things, with more thrown in.