vibe-coding-10-commandments¶
Insight: Vibe coding can be made production-ready through systematic discipline. Key rules: (1) juniors should ask questions not generate code — domain expertise matters more than AI fluency, (2) break large problems into smaller ones before sending to AI, (3) write lots of tests — AI doesn't resist writing them like humans do, and tests catch the mistakes AI generates. Everyone is a "junior" outside their domain of expertise.
Detail: YK (CS Dojo, 2M+ YouTube subscribers) distills intensive daily AI coding into practical rules. The junior/domain expertise insight is particularly relevant: if you're a React expert working in Rust, you should treat yourself as a junior and be more careful with AI-generated code. The testing insight is practical — since AI willingly writes tests while humans resist it, AI-assisted workflows should lean into testing as a quality gate. The problem-decomposition advice echoes traditional software engineering but is reframed: if AI struggles with a task, ask it to break the task down further (e.g., from 20 file changes at once to 2-3 at a time).
Sources
Related: existing entry "AI coding quality is a skill issue" in external/claude-code.md — CORROBORATES