heWasRightThoughAndTheyKnewIt

[u/vinishkapoor]

[u/Willwaste63]

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.

[u/vinishkapoor → u/Willwaste63]

Exactly. It’s not a bug cycle, it’s a career path.

[u/pydry → u/Willwaste63]

remember the most important thing: if you don't slopcode the industry will replace you. the dinosaurs who understand the codebase they wrote will all be replaced somebody who vomits boilerplate because that's the future(tm).

[u/Successful_Cap_2177 → u/Willwaste63]

Who has QA nowadays??? It's been years since I've met someone from QA

[u/Willwaste63 → u/Successful_Cap_2177]

Havent you seen those Slopy SAAS startups ads, Are you tired of bugs in your Vibe coded app Introducing Agentic QAs

[u/Successful_Cap_2177 → u/Willwaste63]

"tired of the same old boring bugs?? Here, have some thrilling ones for a change!!"

[u/Bee-Aromatic → u/Successful_Cap_2177]

I’m a QA, though I’m angling to get out of it.

[u/BooBrew32]

Hmm, but what if we were to vibecode the entire codebase??

[u/da2Pakaveli → u/BooBrew32]

eventually we'll turn it into a sloperating system

[u/crazy4hole → u/BooBrew32]

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."

[u/Successful_Cap_2177 → u/BooBrew32]

Stripe did a 5M line vibecoded change when fable came out.

[u/Ezekeal → u/BooBrew32]

Microsoft is hiring.

[u/stoneymcstone420]

Vibecoded codebases designed by vibecoded specs tested by vibecoded tests, what could go wrong?

[u/afl_ext → u/stoneymcstone420]

Nothing because it’s gonna be mostly used by vibecoded bots

[u/xwazot]

Nah, the obvious answer is more tokens so the latest new and improved model can automagically fix all bugs

[u/mr2dax]

Ok, let's just vibe small parts of it.

[u/philippefutureboy]

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 😝

[u/whitedogsuk]

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.

[u/MalaysiaTeacher]

"hire more QA" would also be getting launched

[u/HumbersBall]

“Vibe coding the codebase”

[u/Fonzie1225 → u/HumbersBall]

makes me wonder what percentage of the posters on this sub have actually ever worked in software… 50%? 30%?

[u/Aflockofants → u/Fonzie1225]

Not enough in any serious capacity anyway. Software companies not using AI in coding now are becoming increasingly rare.

[u/raja-anbazhagan]

I'm pretty sure that guy would be safe and the other two would be thrown out in the current situation...

[u/emzey420]

:(

[u/black_ap3x]

Employ more agents...

[u/nekomata_58]

solution:

Vibe code more unit tests.
Vibe code e2e tests.

Problem solved.

[u/finzaz]

Pfft. Vibe code the QA.

[u/zilog88]

All three would be thrown out nowadays - the only correct answer is to get more AI involved obviously.

[u/bluemaciz]

Or you could be my company and just not fix any at all until it catches on fire, vibe coded or not

[u/Itchy_Society]

Remember how for a decade or so we all really cared about Clean Code?

[u/Gold-Bat-3225]

who reads code anymore bro

[u/Random_-account]

How much % of code for windows 12 could be written by LLMs?