unknown

AI coding tools like GitHub Copilot are creating a phenomenon called 'vibe coding' where developers become overly dependent on AI-generated code, leading to skill degradation and loss of fundamental programming abilities. This dependency results in security vulnerabilities, debugging difficulties, and architectural blindness as developers stop understanding the code they ship. The article argues for using AI as a co-pilot rather than autopilot, maintaining human oversight and continuing to practice core coding skills to avoid becoming liabilities when AI fails.

How AI Vibe Coding Is Erasing Developers’ Skills

kt123123123

As much as I dislike this “vibe coding” malarky, you could make this argument about literally anything that is designed to speed things up. I’ve found sometimes I forget more complicated raw SQL queries because I constantly use Laravel’s Eloquent Query Builder.
Use it or lose it, as they say.

my beef with this vibe coding nonsense isn’t what it’s doing to REAL developers. it’s how it’s opened the door for a bunch of wannabes to SAY they are devs when they aren’t anything CLOSE to being a real developer.
it’s extremely odd to me how there’s this MASSIVE uproar about how “ai” art isn’t real art and yet no one seems to be batting an eye that “ai” programming is somehow “real”.
it’s just more of the american double standard but it’s extremely odd to me that on this DEVELOPER focused platform we even ALLOW discussion of vibe “coding” because it is not real development in any way shape or form.
it’s ok to use “ai” as an assistant but vibe &quot;coding’ is a joke. it’s only a matter of time before every post on here will be “10x your vibe coding. 99% of vibe coders don’t know this ONE trick!”

What I see, the “development way” is changing, will be taken by AI. the developer will now focus on workflows, logic, architecture, etc. leaving the Code to AI

One recent incident that I came across, and an entire codebase was deleted because HR brought on a vibe coder. The senior that was supervising literally watched him input a kernel error to ChatGPT instead reading the error message or logs. This is where we’re heading. The 6 developers that companies are trying to replace with an Ai-supported “Jr Dev” is quickly going to become a justified budget expense to hire on those 6 devs, and it’ll be +6 months for them to clean up the mess.
My advice: have Javascript be your introduction, move onto Python/Go and C, then go to whatever afterwards. If you can’t write 5 stanzas, a switch, or single function without Ai, stop claiming to be a coder, programmer, or developer. You’re killing company codebase and destroying production.

I’m a web developer for over 20 Years. I was working with all kinds of Platforms. The most efficient way to bring Websites to life is, in my case, WordPress. Of course self developed Theme and custom Plugins. Is it called “vibe coding” too, if I use for nearly 2 Years now, a plugin which does add options to the editor, so I do not have to program EVERYTHING by hand? For me, vibe coding means getting into a flow where intuition and experimentation guide the process more than strict plans. Sometimes I code everything by hand, sometimes I use plugins – but either way, I’m actively tweaking, combining, and shaping until it feels right.