Comment by whaleidk
17 days ago
Hopefully this does not count as being uncivil, I just want to cut through what feels like insanity to put my (and at least a few others’) feelings plainly:
If you are one of those devs who heavily uses LLMs at work and you are in a position of relative authority, either as senior+ or something else, and you hand off your LLM code to others to review or “build off of”… we hate you. We don’t want to be your voluntold slop jannies. LLM over use and vibe coding is taking a fairly enjoyable job and making it insufferable. Now I have to sift through 3-10x more lines of code that are written in a non-human thought process using terrible naming schemes and try to find the bug… just to realize that the code isn’t even solving for the correct or underlying problem. Every time I have to interact with a co-workers LLM code, my tasks take weeks longer than they would have. This is including the ones who claim to be exerts in prompting and harnessing and whatever skibidi buzzword is out this week.
You are not saving time, you only think you are because you don’t look closely at the output and send it off to your lowley janitors to deal with. And the people who claim to be running 20 or 30 AI tasks at once what are you even building? If you aren’t literally shipping the next Amazon that’s just embarrassing.
I can not wait for people to wake from this bizarre mass psychosis. I already see co-workers context window getting smaller than free version ChatGPT in an incognito window.
I think it's beneficial to hear this, as I've definitely been on the other side of this before now. So, thanks for sharing.
As much as we can fault the technology and the hype around it, this as much a people problem as anything else. Before AI, this same problem happened with architecture/PoC to implementation hand-offs.
AI is a new tool that a lot of us are still figuring out, but that doesn't excuse poor communication.