Forget the 'feeling', trust the specifications!
summary
Explains why teams should stop relying on intuition and instead trust formal specifications to guide development. Covers using written or machine-readable specifications (requirements, contracts, tests) to reduce ambiguity, improve correctness and communication between stakeholders and developers.
AI-written summary · about
chapters (9)
- 0:00State-driven development intro
- 5:19Vibe coding problems
- 13:12Spec-driven development
- 23:49Setting up SpecKit
- 35:44Clarifying specs
- 36:25Planning implementation
- 42:09Generating app code
- 45:24Key takeaways
- 46:38Q&A
related talks
57mThings That Work So Well for Me I Can't Believe You're Not Using Them
45mPanel Discussion | How to deal with bad requirements in testing?
01h 48mNo Such Thing as Manual Testing and Other Confusions
49mThe Secret to Successful Testing
42mPrototyping with code
57mSetting a Good Example - How to improve your SbE, BDD & ATDD Artefacts
27mSpecification by Example
32mApplying Engineering Principles to Technical Writing