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 know, the show Goblin Slayer had a scene where the older wizard was teaching the younger wizard about magic and the older one said something that stuck with me. Keep in mind I’m paraphrasing here.
young wizards often believe that they are magic casters because they can cast magic, and that’s all they have to do. they don’t realize that a wizard is supposed to be solving problems for their party with magic.
I think this is similar to the new and old devs of today. Old devs are solving problems with software, new devs are writing software to write software. it’s pretty apparent with the current state of node and python package libraries in contrast to more matured ruby and java libraries.
doesn’t matter IMO, software development is dying because the younger devs don’t want to solve the problems anyway and just want to rewrite things in new languages or frameworks. they think they’re solving the problems, but they’re just trading them for different ones.
People who would have gone into finance or received an MBA have been going to tech for a decade now. Every one of them pushes out someone who would have been a real developer.
I’ve also had the pleasure of watching a lot of the generation who’s now complaining as they grew through their journey as developers. I think a lot of them are sugar coating their own abilities. I struggled with many a now illustrious developer whole they banged their head against the wall for hours.
you know, the show Goblin Slayer had a scene where the older wizard was teaching the younger wizard about magic and the older one said something that stuck with me. Keep in mind I’m paraphrasing here.
I think this is similar to the new and old devs of today. Old devs are solving problems with software, new devs are writing software to write software. it’s pretty apparent with the current state of node and python package libraries in contrast to more matured ruby and java libraries.
doesn’t matter IMO, software development is dying because the younger devs don’t want to solve the problems anyway and just want to rewrite things in new languages or frameworks. they think they’re solving the problems, but they’re just trading them for different ones.
People who would have gone into finance or received an MBA have been going to tech for a decade now. Every one of them pushes out someone who would have been a real developer.
I’ve also had the pleasure of watching a lot of the generation who’s now complaining as they grew through their journey as developers. I think a lot of them are sugar coating their own abilities. I struggled with many a now illustrious developer whole they banged their head against the wall for hours.