The Problem: There were Legitimate Business Reasons, but we regret everything anyway. With a title like this one, how can we not make it to the top of Hacker News? This episode we discuss all the reasons you might not want to go down the Microservices r

The problem: Turns out drunk babies aren't funny. It's time for a break. We've focussed too hard, over the last dozen episodes, on bringing you top quality content related to engineering management, organisational culture, and whatever the th

The problem: FAAAAAAAAAAAAAANG. The stars have been gone billions of years now. Black holes burnt out. All but one, where the last dregs of civilization fought over the last dregs of Hawking radiation, before that black hole too ran its course. Now there

The Problem: It's never the API gateway (until it is). Your monitoring is on point, you have a symfony of alerts with appropriate priority levels, runbooks are written and up-to-date, and your services autoscale like an absolute mother hubbard. But

The Problem: You may only know a single tcpdump command, but you're sure as hell going to use it. We're trying something new this week - it's a two-parter! We decided to live up to our name and talk about critical incident response procedures

The Problem: You can't restart PHP if it's not installed. If you're the kind of person who can't stand the clackety-clack of mechanical keyboards, then we're probably not the colleagues for you. clackety-clackety-clack After making

The Problem: You may be a fancy pants Junior Senior SRE Engineer, but Google Sheets is probably Skynet. Job titles probably aren't important, except that they are. This episode, we wrap our heads around exactly why that is, both from your own point o

The Problem: We have no idea how Formula 1 works (but it sure is fun to watch). We hit the ground running in this inaugural epsiode, discussing where the boundary in terms of responsibilities lies between developers and operations. How much should develo