/ writing Notes on engineering — infrastructure, distributed systems, the small choices that compound. Mostly written for myself; published in case it helps someone else.
- (Humans) Yeah (What are they good for?) Absolutely everything. Series · Harness Engineering · Part 5 of 5
- Marked Isn't Enforced Series · Harness Engineering · Part 4 of 5
- Two places to put the types
- Stale Beats Broken Series · Harness Engineering · Part 3 of 5
- What the Harness Can't Prove Series · Harness Engineering · Part 2 of 5
- Stop Babysitting Pull Requests
- Harnesses, Playbooks, and Proof Series · Harness Engineering · Part 1 of 5
- Your tests can't see the waves
- Slop Is Upstream
- Drift Is Not a Bug
- Companies Don't Remember in Conversations Series · The Currency Problem · Part 2 of 2
- Your Agents Don't Have a Memory Problem Series · The Currency Problem · Part 1 of 2
- Steal this blog
- 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