vitaliks.me

Vibe coding is just engineering without process

Aug 15, 2025 · 1 min read
aiengineeringprocess

I keep seeing Reddit threads about "vibe coding" not working and AI assistants "dropping production databases." Let's be honest. Working with AI coding assistants is no different from leading a team of software engineers.

In every team, you have developers with varying skill levels. Any developer with access to the production DB can accidentally drop it. And most of us (if you are lucky, only once) have made a mistake in production. This is why we have built decades of processes. Architecture boundaries, code reviews, access controls, CI/CD checks. Systems that allow teams to ship safely.

AI coding assistants do not need special treatment. Give them the same boundaries, reviews, and access controls you expect from any engineer on the team.

If you treat them like teammates and put the right processes in place, they can be incredibly effective.

But if you are a "vibe coder" (a term I dislike as it really just means an overly optimistic builder) who believes they can ship production grade applications without any process in place, you are taking a high risk of things going wrong.

AI coding agents like Copilot, Cursor, Claude Code, and others are evolving rapidly. They may not be getting smarter, but they are continuously gaining new capabilities, models, and workflows. Some will integrate seamlessly into your team, while others will require careful adoption through guardrails, isolated environments, or stricter reviews. Just like onboarding new developers in your team.

Treat AI assistants like teammates: train them, guide them, and they'll scale your team.