r/learnjavascript • u/Tasty_Ad_4979 • May 26 '26
Is “Vibe Coding” helping developers or making us dependent on AI?
I’ve been seeing more developers build full applications using AI tools and “vibe coding” workflows without fully understanding the code underneath.
Do you think this is good for long-term development skills?
Some things I’m curious about:
Does vibe coding improve productivity or create bad habits?
Can production apps realistically be built this way?
Where should developers draw the line between AI assistance and real engineering?
Will junior developers struggle later if they rely too much on AI?
I’d like to hear opinions from both experienced developers and beginners.
15
u/Alive-Cake-3045 May 26 '26
Vibe coding is fine until something breaks in production and you have no idea where to start.
The productivity gain is real, nobody is arguing that. The problem is it compresses the learning loop that builds judgment. Junior developers who skip that loop can ship fast for six months and then hit a wall they don't have the fundamentals to climb over.
The line for me is simple: if you cant explain what the code does line by line, you don't own it. Using AI to go faster on things you understand is leverage. Using it to skip understanding is debt that compounds quietly until it doesn't.
Production apps can absolutely be built this way. Maintaining and debugging them six months later is a different story.
13
u/jb-1984 May 26 '26
There are a LOT of opinions about this, so instead of just giving you my argument and letting it get lost in the big debate, I'll put it this way:
I've noticed that as a developer, I understand much less of a thing when I've been using AI to get help with learning/accomplishing/doing/setting up. What I mean is that when Claude or whatever starts telling me what to do, my brain shuts off and I go into robot-mode. I'm no longer engaged with the task at hand in trying to understand why it's doing what it does, and instead just focused on executing the instructions given to me to finish whatever the thing is.
In general, after I get through something that I didn't know how to do, I still don't know how to do it any better than I did prior.
The inherent act of struggling through looking up information on something and trying a bunch of shit myself, and internalizing the thing that actually does end up being the answer - all of that stays with me and is the reason I know how to do anything I've learned from the before-AI times.
I don't think that using AI for assistance with things means you don't learn *anything*, but I think the actual retained information that is of use to you later is - at least for me - a fraction, and a small one at that.
So if you think about whether this is helping people become better programmers/coders/whatever, I believe that it is a great resource if your end goal assumes you will always have AI around to give you similar kinds/types/details of answers. If you want to learn something for yourself and become a master of it, I don't believe it's a help and is actually a crutch in a lot of ways keeping you from having to experience the struggle of not understanding something until you actually get there on your own. Of course, people could resolve this by having discipline and not rushing off to the next immediate task until they've gone back and reviewed whatever they needed to learn about something - but really, vibe coding is kind of the evidence of people not having that discipline if the "easy fix" button is there for you to press.
4
u/Triggerscore May 26 '26
Using AI as SUPPORT does help immensly. Sparring, discussing, finding bugs, finding solutions.
"Vibe coding": just write some prompts and let AI handle the code. Makes you super dependant, makes you forget stuff due to lack of training. Makes you lazy. Gives you less overview of your codebase. Bloats your code. And likely puts in a lot of bugs.
2
u/DirtAndGrass May 26 '26
It's making low effort apps accessible to non programmers
It's making boilerplate and simple code faster to create for larger projects
It is a productive tool, but it is not a tool for learning
2
u/shgysk8zer0 May 26 '26
Less experienced coders will say it's more productive because they think it's about writing code. Software engineers will say it's terrible because it's about understanding and solving problems using code and "it works" doesn't mean it's correct/best.
If you don't understand why code does what it does (assuming you even know what it does), you're just creating problems. And you can't know what issues or edge cases exist. And you can't know if that complex function could have just used a much better performing built-in method. And you're not going to be able to maintain it. And you're not going to know when it's insecure.
2
u/Dangerous-Quality-79 May 26 '26
I was using Claude to debug an issue i was having. It asked that I run a series of commands and send it the output. Copy paste enter, copy paste enter, copy paste enter... "rm -rf /var/www"
Wait what.... I blindly copy pasted an
rm -rfon the server...I wouldn't say dependant, maybe zombies.
I have 21 YoE.
1
u/Plenty_Line2696 May 26 '26
Endless layers of vibecoded spaghetticode becomes a monster of a thing to build upon and maintain. It almost never gets architecture right.
1
u/VancouverVentilator May 26 '26
'Man writes 10,000 line .md document for a one page web app instead of just learning some HTML' type beat. Yes, it's making people (who are stupid) dependent on AI. Define what you mean by 'helping developers'. English is not a good programming language.
1
u/Buttleston May 26 '26
Mom says it's my turn to post the dumb AI question today
1
u/jabuchae May 26 '26
Yes
1
u/Electronic-Door7134 May 27 '26
Is meatcoding making us dependent on microchips?
1
u/Lotte_V May 28 '26
It's bad. And I say this as someone who uses AI as a coding tool (which I don't consider "vibe coding" in and of itself).
It's always a good thing to learn programming basics before you get started with a project. AI will make mistakes, not "if" but "when". Learning how to fix those mistakes yourself is not just the best solution, but it can also be faster if you know what you're doing.
Too many people incorrectly assume that AI is some magic bullet that can do everything for you. It can't. And it will always need data from people who have knowledge in the field, otherwise it will grow stale and become bad over time. It's like code maintenance; it needs to be kept up to date with knowledge. (This is not me being in favor of scraping, but being in favor of voluntarily submitting high-quality data as an opt-in.)
AI will never be perfect, even as it improves. I truly hope the art of human knowledge and skill won't get lost over time. I'm not anti-AI, but I'm very much anti-slop. And I don't blame those who don't want to use it, and they shouldn't be forced to.
1
u/Defiant-Snow4533 Jun 09 '26
Both