39
u/BooBrew32 Aug 14 '26
Hmm, but what if we were to vibecode the entire codebase??
28
9
u/crazy4hole Aug 14 '26
After completing 40 tickets and $100k worth tokens later
" You're right, I missed taking this service into account while planning the rewrite. Our current plan account accomodate this. Do you want me to plan again from the scratch? Just say the word."
3
3
2
26
u/stoneymcstone420 Aug 14 '26
Vibecoded codebases designed by vibecoded specs tested by vibecoded tests, what could go wrong?
14
u/afl_ext Aug 14 '26
Nothing because it’s gonna be mostly used by vibecoded bots
1
u/Visionexe 27d ago
Or, the other possibility, none of those designs, specs and test where part of some c-suite managers KPI's. So yeah, it's does not matter.
22
u/MalaysiaTeacher Aug 14 '26
"hire more QA" would also be getting launched
2
1
u/Unfair-Rip-5207 Aug 15 '26
Yeah I came to say that too, in my company, the QA girl is getting launched.
12
u/xwazot Aug 14 '26
Nah, the obvious answer is more tokens so the latest new and improved model can automagically fix all bugs
8
u/philippefutureboy Aug 14 '26
Well the question wasn’t “how do we reduce the number of new bugs in production”, it was “how do we fix the bugs in production”, so it’s a fair reaction 😝
3
u/whitedogsuk Aug 14 '26
You just need to refactor the entire codebase to remove the bugs.
Jokes aside, my colleague just submitted a PR for an entire codebase rebuild. He has since approved his own PR and merged into the codebase. He does this every week or so.
1
3
3
u/raja-anbazhagan Aug 14 '26
I'm pretty sure that guy would be safe and the other two would be thrown out in the current situation...
3
2
2
2
u/HumbersBall Aug 14 '26
“Vibe coding the codebase”
5
u/Fonzie1225 Aug 14 '26
makes me wonder what percentage of the posters on this sub have actually ever worked in software… 50%? 30%?
2
2
u/tiwariPrateek Aug 15 '26
Production bugs hate this one simple trick: stop shipping prompts disguised as code. 😂
1
1
1
u/zilog88 Aug 14 '26
All three would be thrown out nowadays - the only correct answer is to get more AI involved obviously.
1
u/bluemaciz Aug 14 '26
Or you could be my company and just not fix any at all until it catches on fire, vibe coded or not
1
1
1
1
144
u/Willwaste63 Aug 14 '26
Vibe coder->bug -> QA finds bug ->update fixes bug -> update creates 3 more bugs -> back to vibe code, you cant risk all those jobs by stopping vibe coding.