Hot take: Vibe coding doesn’t replace developers — it turns senior developers into small engineering teams
Hot take:
Most people are using “vibe coding” to create demos.
Senior developers can use it to compress entire engineering teams.
I’ve been a developer for 25 years and spent the last 3 months building a full SaaS product with Claude, Codex and a very strict AI workflow.
It’s an uptime monitoring platform: checks, incidents, alerts, status pages, billing, multi-tenant workspaces, regional workers, Stripe, security flows, test suites, docs, launch material.
The AI wrote a lot of code.
But the AI did not build the product.
The process did.
My workflow looked less like:
“Build me a SaaS”
and more like:
- Write the ticket.
- Define acceptance criteria.
- Ask AI for implementation plan.
- Challenge the plan.
- Generate code in small slices.
- Run tests.
- Ask another AI pass to review for edge cases.
- Add regression tests.
- Refactor.
- Update docs.
- Only then move on.
That is not “vibes”.
That is engineering management with AI agents.
The more I used AI, the more important my senior experience became.
Because AI is very good at producing plausible solutions.
But plausible is not production.
Production means:
race conditions, billing edge cases, multi-tenant isolation, webhook idempotency, retries, broken deployments, bad UX states, compliance, observability, test coverage and boring maintenance.
This is where beginners get fooled.
AI makes you feel like you skipped 10 years of experience.
Then production reminds you that you didn’t.
My conclusion after 3 months:
AI massively increases output.
But it amplifies the operator.
A weak developer ships weak code faster.
A strong developer ships stronger systems faster.
The discussion around vibe coding is too focused on “Can non-developers build apps now?”
The more interesting question is:
What can one experienced developer build now that previously required a small team?