Getting software to work is just the beginning
Everything will work In application development, and probably in every IT field, almost any tool will get you to a working result. Any tool, any combination of frameworks and technologies can be strun
Effective software engineering
25 years modeling domains in enterprise and startups. Helping teams build systems that evolve, not explode. DM me if you want clarity before chaos. Model first. Code second.
Latest articles
What AI Context Limitations Teach About Software Development
Ask an AI coding assistant to fix a bug in one file, and there's a decent chance it patches the symptom at the call site rather than the logic several layers away that's actually causing it. That orig
Tech Debt Isn't a Backlog Problem. It's a "Done" Problem.
Technical debt is usually described as a bill that arrives later for a purchase made earlier: speed bought on credit, with the cost deferred to some future date. Ask practitioners why debt accumulates
The Technical Candy Problem in Software Development
Goodhart's Law, software architecture, and the questions it lets teams stop asking
Tooling Is the Icing on the Cake, Not the Cake Itself
There's a recurring message on LinkedIn: Java 8 is legacy. Java 21 is enterprise-ready. Upgrade, or fall behind. Ask the same people directly whether a better language makes for a better product, and
How Do You Tell Your Software Application Is of High Quality? Part 2
Part 2 — Essential and Accidental Complexity Part 1's answer to that question was 'you can't' — and that still stands. No controlled counterfactual exists, and it isn't coming. What's fixable is narro
How Do You Tell Your Software Application Is of High Quality?
Part 1 — Problem Definition You can't. Not with any test you currently run. Every test in a standard suite answers one question: does the software do what it's supposed to do. None of them answer a se
Discovery and Fit Testing: The Two Jobs of a Domain Model
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
Why Expensive Software Development Never Looks Expensive
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
