Notes on engineering — infrastructure, distributed systems, the small choices that compound. Mostly written for myself; published in case it helps someone else.
- The Jobs Aren't Back. They're Different Jobs.
- I Stopped Correcting 40% of My AI's Work.
- Introducing Moment and Facet: Your Domain Model Deserves to Run Before Your Code Does
- Event Storming Is a Language, Not a Workshop
- AI Made My Architecture Deeper, Not Simpler Series · Solo DDD · Part 8 of 8
- The Classification Gap: The Bug That Passes Every Test Series · Solo DDD · Part 7 of 8
- When Jobs to Be Done Meets Domain-Driven Design
- The Candidate Lifecycle: When AI Models Your Domain, Who Confirms It? Series · Solo DDD · Part 6 of 8
- The Gap Report: DDD's Missing Feedback Loop Series · Solo DDD · Part 5 of 8
- Introducing Signal-Driven Development Series · Solo DDD · Part 4 of 8
- The Coherence Problem
- The Single-Seat Architect
- The Reactive Path Has No Vocabulary Series · Solo DDD · Part 3 of 8
- Knowledge Crunching Doesn't Need a Room Series · Solo DDD · Part 2 of 8
- DDD has a solo-builder problem, and nobody talks about it. Series · Solo DDD · Part 1 of 8