/ writing Series
Solo DDD
DDD was designed for teams. I'm building alone. This series is about what breaks, what holds, and what the methodology looks like when you strip away the room, the whiteboard, and everyone else in it.
- DDD has a solo-builder problem, and nobody talks about it. Every serious architect I know agrees: if you're building software for a complex domain, Domain-Driven Design is the gold standard. Evans was right. Vernon was right. The methodology works. But here's
- Knowledge Crunching Doesn't Need a Room Most people think the hard part of domain modeling is learning the patterns. Aggregates, entities, value objects, domain events, repositories — the tactical toolbox. There are books, courses, conferen
- The Reactive Path Has No Vocabulary I've been practicing Domain-Driven Design for over a decade. I've built event-sourced systems. I've implemented CQRS. I've drawn bounded context boundaries, defined aggregates, modeled domain events w
- Introducing Signal-Driven Development Not "done" in the project management sense — not "the sprint ended" or "the stakeholders signed off." Done in the engineering sense. Structurally complete. Semantically consistent. Ready for implement
- The Gap Report: DDD's Missing Feedback Loop In Post 4, I introduced Signal-Driven Development and its core claim: DDD has never had a definition of done. SDD provides one — zero unresolved gaps across a structured convergence process. But I lef
- The Candidate Lifecycle: When AI Models Your Domain, Who Confirms It? This post marks a shift. Posts 1 through 5 gave away a methodology — Signal-Driven Development, the gap report, the three-pass convergence process. That was the community gift. Use it, fork it, adapt
- The Classification Gap: The Bug That Passes Every Test There's a class of domain modeling error that no test catches. No structural analysis flags it. No linter complains. Your gap report comes back clean. Your aggregate has the right number of invariants
- AI Made My Architecture Deeper, Not Simpler The pitch is always simplification. AI will make development faster, architectures leaner, systems easier. Fewer decisions, fewer layers, fewer meetings. Point the model at your domain, let it generat