
Vibing Isn't for Everyone, Part I
12 snips
Jan 7, 2026 Confusion around Vibe Coding takes center stage as hosts tackle a listener's feedback. They explore management's role in project estimates and discuss the advantages junior developers have over their more resistant peers. The conversation parallels early tech disruptions, highlighting how initial skepticism can cloud clear adoption paths. As they assess the future of Vibe Coding, they provide insights on balancing immediate needs with foundational Agile practices. Expect an engaging dialogue filled with industry reflections!
AI Snips
Chapters
Books
Transcript
Episode notes
Executive Vibecoded Project Example
- Jeffrey and Douglas recount Gene Kim's story of an exec who vibe coded a six-month project in five days and only a junior wanted to maintain it.
- Tom responded that this reveals leadership failure and missing incremental delivery practices.
Don't Bypass Teams To 'VibeCode' Work
- Do not treat Gene's story as a recommendation to bypass teams; use it to notice where juniors adopt tools faster.
- Avoid assuming vibecoding by leaders is best practice without addressing core team and leadership issues.
Juniors Can Lead Tooling Adoption
- Jeffrey links vibe coding adoption to Steve Yege's papers about juniors overtaking seniors with AI tools.
- Juniors more readily adopt new tooling and can become the frontier for industry learning.

