The Gap Between Vibe Coding and Production Reality
Comi9689 · reddit · 2026-07-19
A non-programmer spent a month building a SaaS using Claude, only to realize upon getting real users that production environments demand permissions and isolation, not just a slick UI.
Stumped by a friend's question—"Can User A change their ID to view User B's data?"—the author realized they had split auth, database rules, and server functions across isolated Claude chats, effectively assembling a system on a "one prompt, one permission" basis. The accompanying image reinforces this: vibe coding only covers surface prototyping, while production reality requires heavy engineering for auth, access control, data integrity, logging, rate limiting, CI/CD, rollbacks, monitoring, and disaster recovery.
The author concludes by asking no-code/low-code founders what they actually audit before real users touch customer data.
More from coding & agent
- Frontend Textbooks turns long Codex outputs into book-style documents — nbaschez · 2026-07-21
- A Codex harness user says OpenAI’s assistant is less smart-sounding but more decisive — McDonaghMatthew · 2026-07-21
- Octen’s search benchmark is public and reproducible for agent stacks — aakashgupta · 2026-07-21
- Octen says agent search now runs at 62ms P50 with only a 6ms P90 gap — aakashgupta · 2026-07-21
- Users say Codex side chats are becoming part of their real coding workflow — nicoalbanese10 · 2026-07-21
- LithosAI says Kimi K3 is frontier-level for open-weight agentic tasks — JiaZhihao · 2026-07-21