this post was submitted on 09 Oct 2026
130 points (95.8% liked)
Technology
89012 readers
2783 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Makes sense. AI can accelerate experienced coders. I'm ok to see people use AI for helping but NOT for Vibe Coding.
I can only talk from personal experience, but it absolutely does speed up things. I know because I went from working away at one project to progressing many projects at the same time. Starting up new projects I never would have bothered to do in the first place just because the work would have been so tedious and I wouldn't have enough time in the day. Mind you, I don't vibe code things for public consumption. These are all for my personal use, but the fact that they exist at all is evidence contrary to your points.
(Important note: how I use AI in important software is very different from how I use AI for slop projects; the speedups are not as dramatic when you aren't vibrcoding and you actually need good quality; I suspect most AI usage would actually be a slight downgrade for speed unless I delegated them strictly to review and menial implementation; but that actually assumes that I know the language I'm working in very well, which isn't always the case for vibecoded projects: In those cases, the AI slop is probably equal to or better than what I would write by hand because I'm not as competent in elixir or javascript as I am in C or C++)
I feel like this is dishwasher discourse... Washing by hand is faster than the dishwasher by the wallclock; but you don't actually need to rinse as much as you probably do, and you can walk away and do other stuff while the dishwasher is working. If you just sit there and stare at the dishwasher, yes, it's slower, but that's not how people should use it, and that's what most of those studies are showing. Again, that level of sloppiness isn't applicable for all use cases, but for where it is useful, it is very useful.
Listen, I'm a VERY healthy skeptic of AI on a number of fronts, but saying it can't speed things up is just not true.
I feel like I understand where you're trying to come from with the argument about skill degradation, but the flat statement you say here is undeniably false.
I've run this experiment on myself a great number of times.
Your story is correct, sometimes. It's not correct all of the time. Sometimes AI is slower and the output is better (think: pair programming). Sometimes AI gets me the first draft and the cognitive understanding takes time (overall, for me, usually faster, but sometimes slower I will readily admit). I'm really good at reading code, I guess? And still other times it will one shot near perfection (in true slot machine fashion). It'll also produce absolute shit, as well, frequently.
My firm point to you is it's not a blanket truth.
"Degrades quality" assumes developers are already writing good code to start. Unfortunately that just isn't true. For people who know what they are doing and can properly guide it, it absolutely speeds up the menial tasks that plague software engineering. I'm not even a fan of the direction AI is going yet I absolutely see the value here.
For the AI haters, we really need to attack it from a better angle than "it doesn't work" because it absolutely does.
My coworker made a tool(because where we work doesn't allow plugins to it ide yet) that will load our code for context and we can write prompts against it. After we found the source of a big he used his tool and it found the problem in less than a min after asking why we were seeing the behavior in the application( tied up application pools)
That's exactly what I'm talking about. It absolutely does help and works well for very specific tasks. That's a perfect use case.
That's like saying social media can make people more social, when we know that for most people it just leads to addiction.
Human brains are designed to find shortcuts, vibe coding is one of them. I've seen plenty of senior devs fall into this trap.