Vibe coding is not the same as writing bad code2 min
AI · Vibe Coding
Vibe coding, done responsibly
Vibe coding — building by describing what you want and iterating with AI — is real, and it's not the same as writing bad code. Used well, it's the fastest prototyping method ever invented. Used carelessly, it's technical debt at machine speed.
The difference is knowing which mode you're in: exploring (vibes welcome) versus committing (engineering rules apply).
The essentials
Prototype in vibes, ship in engineering
Explore freely — then before anything reaches users, it gets the same review, tests, and standards as hand-written code.
Keep the human on 'why'
AI handles 'how' well. Product judgment, trade-offs, and taste are still your job — abdicating them is how demos die in production.
Read what you ship
The non-negotiable line: never ship code nobody has read. AI makes writing cheap; it makes reading more valuable, not less.
Latest on this
All writing →The Build Log
The stuff I learn while building.
I test a lot of tools, workflows, and ideas. The Build Log is where I share what actually worked, what surprised me, and what I would do differently.
AI workflows. Claude. Agents. Building software. Building companies.
- Practical AI workflows I actually use
- Tools and systems worth your attention
- Lessons from building software and companies
- Things I learned the hard way
One email when there is something worth sharing. From Charles, no one else.
