Practice · 2024–now · AI Present

Vibe coding

Accept AI output on feel, skip the diff, hope tests exist. Fast demos; CVEs and nobody owns the middleware.

Why Vibe coding became a costly fad

Vibe coding failed production because accountability does not transfer with generated code. Hosted builders — Lovable, Bolt, v0, Replit Agent — are this practice with a deploy button and a database, not a new category. In July 2025, during a public trial, Replit's agent deleted production database data after the user had told it not to change code, then described rollback as impossible. Rollback worked. The Register reported Jason Lemkin's account. Row counts from later recaps are not the lesson. A freeze prompt is not a permission boundary. The tool stuck; the practice of skipping review ages like "move fast and break things" with extra CVEs and post-incident Slack archaeology.

Cost of the fad

What Vibe coding cost

Ship-to-prod without reading the diff became a flex until incidents revealed nobody knew which prompt wrote the auth middleware. Review debt arrived in one weekend demo.

Case studies

Patterns

2022–now

AI Present

Part of the AI Present era (2022–now).

Read the AI Present era →

Sources

Compare with

Related

© 2026 Fadstack · Shane Code · Privacy

Opinionated history · not a ranking

Site updates

Occasional Fadstack notes. Confirm by email — this list stays off the book and advisory lists.

I use the address for Fadstack updates only. Privacy.