Panel about vibe coding
summary
Panel argues AI shifts code work from crafting to oversight, with concrete failures and wins: Cloud Code and Claude repeatedly fix then break a socket flow across three hours until English spec reveals the bug, Cursor once destroyed production for a sleepy engineer, a hackathon team prototypes a calendar feature in one day using Bold and Figma Make, an experiment after 450 hours of vibe coding finds a fake testing engine simulation that only mimics failures.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:08What is vibe coding
- 2:15Unexpected AI behaviors
- 6:52Vibe coding with AI
- 9:38AI code impact on quality
- 13:11AI-assisted workflows
- 17:09Human oversight role
- 21:25Psychology of AI tools
- 26:40AI code risks
- 31:59Skills for AI tools
- 35:50Evaluating AI output
- 37:38Team vibe coding
- 41:14AI-driven teams forecast
- 44:29AI tool accessibility
- 46:57Closing
related talks
51mLive Panel Discussion: Less Code? More Vibes? Web Dev in the AI Era
30mVibe Coding That Actually Works
50mPanel: Beyond The Vibe: Code Quality First
46mPanel Discussion: Beyond vibe coding: Expanding AI’s role in delivery
05h 07mVibe Coder Conference 2026 - Day 1
46mKeynote: The Right Vibe: The Role of Community in the Age of AI
06h 03mVibe Coder Conference 2026 - Day 2
26mMaking Vibe Coding a Core Skill
