The Era of Vibe Coding: Why High-Skill Engineers Are More Critical Than Ever
summary
Builds a custom Linux OS called MaruxOS using Claude Code and shows concrete failures: an automated decision to replace libraries leads to a 70-file swap that crashes the kernel and requires rollbacks from detailed worklogs to recover, and an ARM64 Raspberry Pi patch wastes 5-day wrong hypothesis time until a dead serial adapter is found. Argues that LLMs hallucinate and forget architecture, so engineers must provide verification, observability, documentation, and rollback systems for safe AI-native development.
AI-written summary · about
chapters (12)
- 0:00Session introduction
- 1:04Vibe coding era importance
- 3:57AI hallucinations verification
- 4:40GUI file manager failure
- 8:11System rollback importance
- 10:18Raspberry Pi boot failure
- 14:53Observability tools root cause
- 16:46AI hallucinations evidence design
- 17:51AI dementia documentation
- 21:04AI environment design responsibility
- 22:53Skilled engineers role
- 23:58Q&A
related talks
47mPanel about vibe coding
16mVibes won't cut it
28mBeyond the code: Rediscovering the timeless skills of software engineering in the AI era
38mNobody Pages the LLM: Engineering Rigour for Vibe Coding
17mSoftware Engineers Are Tomorrow's Processor Engineers
43mCode Review in the Age of Vibe Coding
06h 03mVibe Coder Conference 2026 - Day 2
32mFrom Vibes to Outages: Riding the AI Code Wave