[hgoel]

Using vibe coding for frequent PRs seems insanely reckless.

In my scientific computing environment, the majority of my vibe coded output goes to one-off scripts, stuff that is not worth committing (correcting outputs, one-off visualizations, consistency checks), and anything worth committing gets further refined to an extent that it pretty much can't be considered vibe coded anymore. It's simply too risky, any bugs would propagate down to decision making for designing new, expensive instruments.

I imagine that the cost and trust risks in enterprise environments are similar, so this seems very reckless.

AI Agents have helped up my productivity, but that's specifically because I can focus on the science, and delegate the auxiliary things to AI. I also believe I get this productivity out of them because my supervisor really drove home how hard I need to go on consistency checks and years of having my visualizations nitpicked (so I am able to do the same to AI and recognize when results are suspicious).

[stackskipton]

Most people don't care. Leadership is demanding feature, feature, feature. IC are worried about losing their jobs and outages rarely cost most business actual money. So garbage gets shipped, outages rise, everyone is burned out but since they can't find another job, they remain.

[chii]

In this situation, you raise the issue with management, with a paper trail that Cover Your Ass, that the pace is unsustainable and bugs will continue to accumulate faster than it can be fixed. Make sure that you are not responsible for it and ensure this is known by all (including management).

You then continue to vibe code as instructed by management. No burnout because you are not responsible anymore.

[stackskipton]

People still get burnout if not from constant pages, the late nights and worry about their job.

[teaearlgraycold]

I love vibe coding for little tools like that. Tools which can have their outputs quickly validated, and then throw them away. Like a jig in woodworking.