Archive
On DDD, architecture, and the semantics of complex domains.
You didn't understand the model. You completed it.
When you read the model the AI handed back and nod, the meaning does not come in the answer. You put it there. That changes who can answer for the cuts.
Where the cuts fall: why complexity is decided before the code
If code were the problem, the machine that now writes it would have solved it. It didn't. The difficulty didn't disappear. It moved to where it had always been, the model.
Complexity is not where you think: why complex code costs nothing until someone reads it
Is complexity in the code or in the reader? A synthesis drawn from Hickey, Dijkstra, Ousterhout, and Parnas. Entanglement is objective, but its cost only exists once measured in understanding.
Ubiquitous language is not a glossary: why your accounting model speaks the wrong language
The hard problems in software are problems of meaning. When the model and the business stop speaking the same language, the debt you accumulate is not technical. It is semantic.