I'm Tomas Basham, a software developer in London, working on backend services and the infrastructure they run on. I write about Go, Rust, cloud and operations, and in my spare time I bake sourdough, hunt for the best burger in town and tinker with electronics and 3D printing.

Most modern software services attempt to provide a system that is available 100% of the time to millions of users around the world. However this provides many challenges in respect to reliability and scalability that are not easily solved with traditional software development and operational methodologies. In this article I...

This is how I use git either working as part of a team or individually. I use an amend/rebase mutable-history workflow where each idea is always represented by one commit. I never make checkpoint commits, and I only need to write git commit messages once per feature (and perhaps amend...

Articles

In an earlier post I described a mismatch: I want slow, deliberate, many-voiced feedback before work starts, and fast, unambiguous, solitary feedback once it does. The resolution was that these aren’t contradictory preferences — they’re the same principle, matching the feedback mechanism to whichever oracle can actually answer the question...

I recently worked out why I find infrastructure and platform work so satisfying: it rewards fast, unambiguous, non-negotiable feedback over slow consensus. The system either works or it doesn’t, and it tells you which almost immediately, without needing a committee to agree first. Then I noticed I hold what looks...

I’m an application developer by trade. I ended up working in infrastructure and platform engineering out of necessity - someone had to run the Kubernetes cluster, someone had to own the cloud account - and somewhere along the way it became the work I love most. It took me a...

There is a particular kind of institutional blindness that develops when nothing has gone wrong for a while. It is not laziness, exactly. It is not negligence in the obvious sense. It is something more insidious: the slow, unannounced erosion of urgency that comes from the absence of consequences. In...

Infrastructure teams tend to discover the same problem at different points in their growth. Someone adds a resource to the wrong workspace, a plan runs against the wrong state file, and suddenly you are staring at a proposed deletion of something critical. The instinct is to consolidate — one workspace,...

Throughout this series, I’ve challenged several technical trends in modern web development—from JavaScript-heavy SPAs to utility-first CSS and the abandonment of progressive enhancement. But these technical approaches don’t exist in isolation; they both shape and are shaped by how we organise our teams. In this final article, I want to...