Christian, AWS Hero and Solution Architect at Bundesliga, shares his journey and hard-won lessons from adopting spec-driven development with AI coding assistants at enterprise scale. Learn when to use specs vs vibe coding, how to build effective steering documents, and practical strategies for helping engineering teams transition from traditional development to AI-assisted workflows. Discover the difference between spec-driven and vibe coding approaches, when to use each, and how to build effective steering documents that guide AI assistants. Christian shares enterprise adoption strategies that actually work, including the show-and-tell approach to reduce AI adoption fear, treating AI as a peer teammate, and creating centers of excellence for sharing learnings. We explore custom agents and the single responsibility principle, context engineering over prompt engineering, and dive into exciting re:Invent announcements like Lambda Durable Functions. Whether you're leading engineering teams, exploring AI-assisted development, or looking to optimize your development workflow, this conversation offers practical insights from real-world enterprise implementation.

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related