@DeRonin_: my friend asked me to review the code in his app tonight "just take a look and tell me what's wrong" what I found: > 22…
Summary
A developer describes discovering extreme bloat in a friend's app—220 endpoints, 40 secrets, 309k lines of code—and rewriting it with Claude to 15 endpoints, 2 secrets, and under 30k lines, arguing that vibe coding without engineering discipline leads to chaos.
View Cached Full Text
Cached at: 05/20/26, 10:36 PM
my friend asked me to review the code in his app tonight
“just take a look and tell me what’s wrong”
what I found:
220 API endpoints. only 20 actually used 40+ secrets in env. only 2 needed to run the project 309,000 lines of code 240,000 lines of documentation nobody reads 1,000,000+ lines of agent logs in markdown files files with 5,000+ lines and zero architecture tests that test.. nobody knows what
he was mass-proud of this. “look how advanced my agentic setup is”
dozens of agent roles. skills files everywhere. knowledge base management that manages nothing. a loop that builds features the product doesn’t need
I rewrote the whole thing for tonight with Claude help
same functionality. clean architecture. proper tests. fraction of the code
the result:
220 endpoints → 15 40 secrets → 2 309k lines → under 30k zero logs clogging the repo every test covers a real scenario
here’s what nobody wants to hear:
vibe coding without engineering discipline is just organized chaos with a nice terminal output
the agent doesn’t know what your product needs. YOU do. if you can’t explain what each file does and why it exists, you don’t have a codebase. you have a mess that happens to run
clean code > clever code. every single time
study this.
believed that this work will take 20 mins to review
into the end it took the whole night while i’ve been into the train lol
but fren was happy
Similar Articles
@mattpocockuk: Vibed out an app today and I haven't looked at the internals at all Things are going wrong with it, I'm scared and frus…
Matt Pocock shares how, after vibing out an app and facing issues, he remembered the /improve-codebase-architecture skill as a helpful tool for fixing things.
@shugarDadddy: Before you launch your vibe coded project, run this prompt first: “Perform a comprehensive audit of the application, co…
A tweet thread shares a comprehensive prompt for auditing vibe-coded projects before launch, covering security, reliability, concurrency, accessibility, and UI consistency.
@no_stp_on_snek: Grok 4.5 Review - I ran out of tokens for the week. Wrote an free iOS/Android app called "Hermes Go". Submitting to the…
A user reviews Grok 4.5's agentic coding capabilities, detailing how a 32-hour session with 104 prompts resulted in a fully functional Flutter app (Hermes Go) with 33k lines of code. The model autonomously reverse-engineered APIs and iterated based on feedback.
I'm going back to writing code by hand
The author reflects on rebuilding a Kubernetes dashboard tool, arguing that while 'vibe-coding' with AI accelerates feature development, it often leads to architectural bloat and technical debt without human oversight.
@eng_khairallah1: https://x.com/eng_khairallah1/status/2055579146684936644
A detailed guide explaining the concept of vibe coding and providing a step-by-step tutorial on how to build apps using Claude for free, targeting non-coders.