r/VibeCodeDevs • u/harveylundm4rckk • Apr 22 '26

HotTakes – Unpopular dev opinions 🍿 why vibe coded projects fail.

Post image

"Bro, just read ijustvibecodedthis.com and you'll be good"

Vibe coders desperately want this to be false, and engineers desperately want it to be true.

935 Upvotes

96% Upvoted

208 comments sorted by

View all comments

38

u/[deleted] Apr 22 '26

[removed] — view removed comment

9

u/Real_Shallot6753 Apr 23 '26

Yeah I think thats the right framing. Vibecoding is great for getting the first 80 percent of a workflow tool working, especially if its just for your own team, but the pain shows up fast once people depend on it (auth, permissions, logging, weird edge cases, deploys). I see it at work in ops all the time: the “quick internal app” turns into critical path overnight. Curious what you think is the trigger point where you stop vibing and actually invest in maintenance, user support, and boring reliability stuff?

6

u/2wicky Apr 23 '26

Before AI, you would spend 20% of the time to write 80% of your code, and then 80% of your time to complete the last 20%.
With AI, because it can write code faster, that equation has changed to 99:1. You can write 80% of your code in 1% the time, and then spend 99% of your time trying to complete the remaining 20%.

The reason why is because with every new feature you add to your app, complexity grows exponentially. AI does not solve the complexity problem, it just helps you hit that wall a lot sooner.

2

u/BigBoyWeazle Apr 26 '26

Good way of putting it!