this post was submitted on 15 Sep 2025
135 points (82.6% liked)
Technology
75162 readers
1580 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
If you are wondering how it could possibly be “worth it” the end of the article has this.
So vibes. Vibe coding is “worth it” because people got good vibes.
The research shows that - while engineers think AI makes them more about 20% more productive - it actually causes an approximate 20% slow-down.
AI cannot use logic or reason. Everything it outputs is a hallucination, even if it’s sometimes accurate. You cannot trust anything it outputs.
Research shows that - while people think having more people in the household gets the housework done faster - babies actually cause an approximate 100% increase in time spent on housework.
Children cannot use logic or reason. Everything they output is brabbling, even if it sometimes resembles actual works. You cannot trust anything they say. Parents are stupid for having them. (/s)
Developers see AI as a "child" that might need many years to grow up, but it's still worth all the trouble they go through. It's an emotional choice, not a rational one.
If I try to get it to do more than predict the next two lines of code it's gonna fuck something up. A nervously laughable thing I saw at work was someone using a long spec file to generate a series of other files and getting high praise for it. It was the equivalent of mustache templates but slower and with a 30% chance of spitting out garbage. There was also no way to verify if you were in that 30% zone without looking through the dozens of files it made.
As someone right there in the trenches getting hired specifically to clean the slop up, I don't buy this survey at all and I'd be very suspicious of any "senior dev" that participated in it cause...where are they? I'm not seeing them when I go in to my clients offices because they all got axed. I do see a lot of junior prompt monkeys though.
I'm a senior dev and I want nothing to do with AI. By the time I understand what I want well enough to describe it in a complete sentence or paragraph, I can just write the fucking code myself. I figure it out as I go.
The whole point of having devs under you that is to be able to trust them to get the job done and do it right. You want to be able to delegate tasks to them and not have to peek over their shoulder every five fucking minutes to be certain they're not making a mess of things.
I seriously doubt AI will ever be able to replace that. Not until they figure out how to make it afraid of fucking up.
As a senior dev I have found AI useful for auto completion (where you see beforehand what it wants to write directly in Visual Studio) and code analysis (as it does find some bugs and can give good hints for code structure). I would never trust it with anything even remotely complex though.
It kinda scares me that people trust it enough for "agent mode", as giving it direct access to change stuff directly has simply put never worked.
Yes. It's extremely helpful when I'm doing a refactor and can just go TAB TAB TAB TAB Oops not that TAB TAB done. Saves me a lot of time with the boilerplate, but is very bad at the logic portions.
You do refactoring with auto complete?
Perhaps senior devs are more likely to use more granular, step-by-step, controlled prompting. Asking it do write specific functions in specific ways and following specific approaches and conventions instead of just "do me an app, robot bro".
That’s actually how I am using AI for my work (web dev, pls don’t hate me). If I am stuck or have some tiny function missing for a task I ask AI, check their output - if it’s garbage I continue on my own again or if it’s usable I review the output and continue from there. Also, I think AI can be neat for „rubberducking“ when I am debugging some stupid shit and point me in directions I haven’t looked before.
Similar to how I have found success with it. Is it revolutionary? No, not at all. But it's a variable sized (big for some use and nonexistent for other use) incremental tool that requires a new skill set to use effectively.
Mix in all of the hype and its easy to see why people are confused and why some get different results.
But surely you test the code and review it, right? That's how you reinstate trust in what it outputs?
Disclaimer: I've never used AI to code, not even copilot.
Based on my coworkers... no.
They get the Ai to write the code, and the tests.
Then hand it over to me to review and test.
Its all overly verbose, does things that are not required or desirable, and insists on re-writing existing code to match its own style.
I hate it passionately.
Damn. 😢
Sounds awful. I would just reject these PRs, dude. Tell them that AI is good for scaffolding and creating a draft, but you gotta maintain the human quality assurance, and that's not your job, it's theirs.
You mean rewrite it all from scratch? If you have any kind of standards that is what you end up doing. If you know what you’re doing you do it right the first time and move on. Using AI for coding it like trying to babysit the most inept, inexperienced intern to ever walk the earth. It wastes time and the end result is far worse.
That's what I'm afraid of, and it doesn't seem like employers are aware of this in general. Irks me especially as a consultant.
It'll sometimes do dumb and/or redundant or too complicated shit. Pile up a couple of those and your codebase can get unmaintainable fast.
I find if you give it small chunks and keep an eye on it, it's great.
I think one of my recent prompts was "Create a procedure that creates an example configuration file with placeholder values. If a config file doesn't exist on start, give a warning and create the example config."
It also works great as a replacement for an ORM.