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.

Vibe coding failed production because accountability does not transfer with generated code. It works for throwaway prototypes and hurts when security and edge cases matter. 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

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

Context

Demos consolidate; evals remain

AI pair programming changed how code is typed faster than how it is reviewed. Agent frameworks and standalone vector stores sorted into demos versus durable plumbing; mid-market RAG folded back into Postgres. The permanent layer is familiar: evals that gate deploys, model routing for cost, tool protocols instead of plugin snowflakes, and humans who own production. Autopilot rewrites and vibe-shipped auth middleware are still big-bang migrations with better slides — and a longer on-call.

Compare with

Related

© 2026 Fadstack · Shane Code

Opinionated history · not a ranking