@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…

X AI KOLs Following News

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.

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.
Original Article
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

I'm going back to writing code by hand

Hacker News Top

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.

Am I the only one starting to get 'Vibe Coding' fatigue ?

Reddit r/AI_Agents

A developer shares their fatigue with 'vibe coding,' noting that while AI agents speed up initial creation, they introduce significant architectural debugging challenges and technical debt in complex repositories.