Specs first, code later (or how I build software in the AI-DLC era)

As AI-driven software development became part of our lives, writing specs before touching anything code-related became the natural thing to do. A structured specification captures what the system should do, how it should behave at the edges, and what "done" looks like. Then AI takes it from there. The workflow behind this is AI-DLC, a three-phase lifecycle: Inception (AI proposes the architecture), Construction (AI generates and iterates on code from your spec), and Operations (AI monitors and patches). Developers steer at each gate, but AI does the building. In this session I'll walk through a real project built this way, show where a good spec caught bugs that tests missed, and demonstrate when rewriting your spec becomes faster than fixing the code. You'll leave with best practices for writing specs, practical rules to follow, and a workflow you can try on your next feature.