On domain understanding, engineering discipline, and moving fast without losing control
Software engineer and architect. For more than twenty years I’ve been building software for complex domains. Along the way I’ve learned that good software starts with understanding the domain, not the technology. This blog is where I share ideas about software architecture, engineering discipline, AI-assisted development and the lessons learned from building systems that have to work in the real world.
Markdown supported · ⌘↵ to post
Adam Lewis
The clarification step is the one I see skipped most often, so it is good to see it named as work rather than overhead. I keep the questions and their answers in the spec itself, and the agent checks back against them as it builds. A surprising amount of review argument disappears when the ambiguity was settled in writing first.