The two senior engineers in my org (in a FAANG) who vibe-code the most have lost literally all of their skills. Their code has become terrible and their judgment even worse.
A very similar topic was discussed here: https://news.ycombinator.com/item?id=48392004 and I make the exact same conclusion:
All of this makes me selfishly excited for my own future. It's glaringly obvious that anyone who's a heavy user of LLMs is atrophying their skills in real-time. I have yet to meet a single person for whom it's not the case. But I essentially completely stopped using them for software engineering (why isn't really relevant, but it's not because od this skill atrophy). So as the skills of everyone else is diminishing, mine is proportionally raising.
It has never been easier to get better than others. You don't need to put in more effort, just the same effort as you always have, and others will do the job of losing their skills for your own benefit.
I recently did a manual exercise to force myself to keep my skills from decaying too much after about a year of using agents exclusively. My ability to go from a blank slate to software was indeed in the toilet, but my ability to reason over and edit code seems to be surviving fine. I suspect that your LLM-pilled coworkers' judgment issues are related to laziness that LLMs have enabled, rather than an inherent property of LLM use.
You're making the right call there. I've felt it, seen it around me personally. That study is terrifying.
I'm no code ninja at the best of times. It's scary to hear that's happening to top engineers.
I need an exit strategy. Anyone else come off AI?
Are you actually seeing any signs that we’re going back to how software was written before, and needing those skills in the same way? Because I sure am not seeing that right now. As someone who vibe codes 100% and has become managements favorite, while being more or less allowed to break the platform every other release I know my skills are atrophying. But it’s taking me different places in my career entirely. There’s a path to managing other engineers now that opened years before it would have previously. Even writing this makes it sound ridiculous, but that’s what’s infront of me right now. There is an entirely other set of skills that I’m interested in sharpening now. Definitely no more sitting down several hours per day and meeting about system design and integrations with others.
> two senior engineers in my org (in a FAANG) who vibe-code the most have lost literally all of their skills.
Unfortunately FAANG incentives this behaviour with their token leaderboards and general push for velocity over anything else (other than goog maybe)
The article is saying that using AI degrades certain skills when AI is not available. You're claiming that AI is making people less effective even when they have access to AI. I'm skeptical of your claim.
The article's claim is probably true, but not really an argument against AI. Using keyboards degrades my ability to write by hand but that's not a good argument against keyboards. AI will become another tool that allows us to operate more effectively and at a higher level of abstraction. Just like keyboards and Python.
Now, we still occasionally need people who can write assembly (and do calligraphy). But mostly we don't.
This is the most important point: it seems like AI tool use undermines one's ability to use the AI tool.
I did stop because I noticed the severe atrophy after using them for a year. Never again.
As someone who was self taught as a programmer and has a reasonable high level understanding of some CS concepts but not lots of experience applying them, and no good mentor, I’ve found working with an LLM really englightening. Asking Claude to think about “good ways to structure this” or asking how similar problems get solved in industry or high profile projects has really helped me design better solutions and avoid painfully reinventing wheels (recent eg was for a plugin type architecture).
I think a lot of academics and researchers who code but aren’t software engineers or CS majors are going to benefit, provided they take the time to prove what the model does and are curious about whether it’s doing something sensible!
Relative to a 1% coder hand rolling something then yes it’s AI slop etc. but it’s prob still raising the bar generally.
Another tactic is to use LLMs to help you learn. That's another way to approach "It has never been easier to get better than others."
Avoiding tool use because you're afraid you won't be able to use the tool responsibly is not likely to be a winning strategy in the end. Learning to use the tool well is much more effective.
My friends can't ride horses as well as they used to, they've been using cars to get around too much.
Sure horses are more efficient, but cars are faster and more convenient, and allow you to get a lot more done.
Also cars will get better in our lifetime, horses are horses.
Idk man my system design game is better than its ever been because I put in the effort to use these tools and recognize they can't do software design better than I can and because I've increased the scope of what I'm building I often have to think more deeply about the problem up front. A typical speccing sessions lasts a few hours for me on big work before I have AI start writing that work where I'm just going back and forth on what I want, points of consideration for performance, usability, structure etc pushing back on where AI (always) chooses the most naive way it wants to do something.
Every time I see an anecdote like this, A it reaffirms my belief that FAANG devs are fairly mediocre on the whole (not saying this is you, obviously there are good FAANG devs) and B it reaffirms my belief that the developers who kind of give up their thinking like this are really using the tool wrong or didn't really care about the work before AI either so its now just a quick means to an end.