Something’s been bugging me about how new devs and I need to talk about it. We’re at this weird inflection point in software development. Every junior dev I talk to has Copilot or Claude or GPT running 24/7. They’re shipping code faster than ever. But when I dig deeper into their understanding of what they’re shipping? That’s where things get concerning. Sure, the code works, but ask why it works that way instead of another way? Crickets. Ask about edge cases? Blank stares. The foundational knowledge that used to come from struggling through problems is just… missing. We’re trading deep understanding for quick fixes, and while it feels great in the moment, we’re going to pay for this later.
You’re right in that the goal is problem solving, you’re wrong that inability to code isn’t a problem.
AI can make a for loop and do common tasks but the moment you have something halfway novel to do, it has a habit of shitting itself and pretending that the feces is good code. And if you can’t read code, you can’t tell the shit from the stuff you want.
It may be able to do it in the future but it can’t yet
Source: data engineer who has fought his AI a time or two.
Very “back in my day” energy.
I do not support AI but programming is about solving problems and not writing code.
If we are concentrating on tool, no developers and use punched card as well. Is that a bad thing?
You’re right in that the goal is problem solving, you’re wrong that inability to code isn’t a problem.
AI can make a for loop and do common tasks but the moment you have something halfway novel to do, it has a habit of shitting itself and pretending that the feces is good code. And if you can’t read code, you can’t tell the shit from the stuff you want.
It may be able to do it in the future but it can’t yet
Source: data engineer who has fought his AI a time or two.
Of course I use as well on a daily basis for coding and AI is shit.
Again, I in no way support AI, I just think that the argument made in the article is also not good.