Development PracticesConference40min
Vibe Coding vs Context Engineering vs Spec-Driven Development: When to Use Each
This talk compares Vibe Coding, Context Engineering, and Spec-Driven Development for AI-assisted feature delivery, demonstrating their strengths and trade-offs. Through practical demos, you'll learn when to use each approach—from rapid prototyping to production-ready releases—and how to combine them effectively for speed and maintainability.
talk.summaryAiDisclaimer
Ron DagdagThomson Reuters
talkDetail.whenAndWhere
Thursday, April 23, 10:55-11:35
Banquet
AI can speed-build features, but not all approaches are equal. We’ll compare three styles you’ll see in modern dev teams: Vibe Coding, Context Engineering, and Spec-Driven Development. You’ll see three concrete demos: a vibe-coded UI whipped up from a single prompt to highlight speed and pitfalls; a context-engineered flow that plugs in project docs, APIs, and tool permissions to produce consistent results; and a spec-first pipeline where contracts generate types, tests, and CI gates, turning AI output into maintainable PRs. By the end, you’ll know when to reach for each approach—ideation, delivery with guardrails, or production-grade releases—and how to blend them without losing momentum.
Ron Dagdag
Ron Dagdag brings over 25 years of experience as a software artisan to his role as Research Engineering Manager at Thomson Reuters, where he leads teams to develop transformative AI solutions. In addition to his professional responsibilities, Ron is an active member of the tech community, recognized as a Microsoft MVP in AI, Mixed Reality, and IoT. Ron is an international speaker, sharing his knowledge at industry events, and remains an active maker and tinkerer with a passion for Augmented Intelligence. 🚀 Code > Create > Coach > Repeat.
