alt Hacker NewsThe forcing of competent engineers to vibe code is something I’ll never understand. Also, I’ve heard rewriting people’s vibe coded efforts being a substantial issue, everything that engineers do nowadays seems to be code review.
Replies
Guys just go and ride it.
It's their money. They decided to do this. They think you guys are stupid.
Suck. Them. Dry.
Or say goodbay, which is what I did on my previous role when the BS started to get obvious.
Now I do LLM-assisted coding on my own terms. I decide what to do, review output and push back agains overengineered BS.
But I'm a lucky one, as far as I can see.
---
NO-ONE is going to be able to understand the the amount of slop created by unchecked LLMs.
The path we're going forward is very clear, given how rapidly top-tier software has been degrading when they decided to pressure devs into this stupidity.
It would be horrible to rewrite. Not the first commit or whatever. But after a few weeks of people not reading the code it looks more like a write only code base. I refused to go full vibe/agentic coding. So I got to see what was happening. This was only over a short period of time mind you.
There was a lot of duplicate and triplicate methods. A lot of the classes were is-a related without inheritance, not the biggest deal but it was becoming a mess.
Code I used to know well was more or less gone. It was rewritten in a way that wasn't the same approach and had lost lessons learned. Some of it had real battle wounds baked into it. Things qa passed the week before were broken in places no one thought they touched. A good deal of tests were useless or didn't mean anything for production.
Code review is more or less impossible for me. I can read maybe a 1k line change. 20-30k changes all the time? You end up saying "sure buddy lgtm". We had someone put a 200kloc change for a new feature using a 3rd party tool no one had used before. No clue, but it was not my business apparently because we needed to be more individuals now that we were using AI