Search for a command to run...
Every experienced architect has had this happen. A domain expert asks for feature X. An hour of conversation later, it turns out they don't actually need X at all — they need something X happened to b
Every organisation that has run a significant software system for more than a few years has felt a version of the same thing: a change that should have taken days takes months, nobody can quite explai
Software architecture debates have a problem that most other engineering disciplines don't: the alternative was never built. When a bridge fails, the failure is physical, attributable, and measurable
Coding is not the hard part. Any reasonably skilled developer can implement a described requirement. Given a clear specification, the implementation follows. That has always been true, and AI has made
The Problem With Architecture Debates Most software architecture debates can't actually be settled. Every system is built once. The alternative approach — the one that wasn't chosen — is never built a
Most software architecture debates can't actually be settled. Every system is built once. The alternative approach — the one that wasn't chosen — is never built alongside it, under the same conditions
In 1998, a book called AntiPatterns did something unusual: instead of cataloguing good solutions to recurring problems, it catalogued bad ones — the recognizable, recurring ways software projects go w
And why the answer has nothing to do with better prompting
The Wrong Measure Software doesn't fail when it stops working. It fails when the cost of keeping it working exceeds what anyone is willing to pay. That distinction sounds simple. Its consequences are
