The outsourcing era showed that making code cheaper moves the real cost from production to comprehension. AI-generated code makes that problem more acute. ...
I have over 25 years of development experience. My current role is vice president of development and architecture where I lead a team of 80+ devs, QAs, and architects. By any measure, I am one of those “engineer level” developers you speak of.
Yes, LLMs are a tool, but it’s a tool one should use sparingly. LLMs are pattern recognition machines and are great for routine, been-there-done-that type development. For anything that deviates from the norm, LLMs will try to force everything back into common patterns… even when those patterns are not correct. A well designed system can be mangled into junk because the LLM doesn’t have enough context or because something is new.
Be skeptical of the rave reviews around coding agents and the use of LLMs for development. Much of the hype seems tied to developer skill. Less capable developers can use LLMs to appear more capable than they are. For good developers, LLMs seem to erode their skills as they rely on the tool instead of their own knowledge. I have seen this first hand.
Overall, it seems LLMs raise skills of bad developers and hamper the skills of good developers. It’s creating a bunch of middling developers who are incapable of handling anything novel or complex.
I’m not pro AI or anti AI. I am anti big tech though, which makes the discussion more complicated.
Regarding escalation, a non coding team lead isn’t a dev. A CTO isn’t a dev. A software architect isn’t a dev. A software developer is a dev. That’s not an escalation, it’s a fact.
Just because you lead a team of devs, doesn’t mean you are a software developer, you could’ve gone to business school, never written a line of code and just started leading a team of software developers because you learned “how to lead”. And there are different kinds of team leads, those that get their hands dirty and those that don’t.
So no, being a CTO, CEO, or whatever C you want to put in front of your title doesn’t make you “far exceed” any qualification. I actually think that kind of thinking is the problem workers are underpaid: people who lead actually often exceedingly overestimate their abilities in the craft they lead. “I lead a team of athletes, that means I’m a good athlete”. Do you understand how crazy that sounds?
I have over 25 years of development experience. My current role is vice president of development and architecture where I lead a team of 80+ devs, QAs, and architects. By any measure, I am one of those “engineer level” developers you speak of.
Yes, LLMs are a tool, but it’s a tool one should use sparingly. LLMs are pattern recognition machines and are great for routine, been-there-done-that type development. For anything that deviates from the norm, LLMs will try to force everything back into common patterns… even when those patterns are not correct. A well designed system can be mangled into junk because the LLM doesn’t have enough context or because something is new.
Be skeptical of the rave reviews around coding agents and the use of LLMs for development. Much of the hype seems tied to developer skill. Less capable developers can use LLMs to appear more capable than they are. For good developers, LLMs seem to erode their skills as they rely on the tool instead of their own knowledge. I have seen this first hand.
Overall, it seems LLMs raise skills of bad developers and hamper the skills of good developers. It’s creating a bunch of middling developers who are incapable of handling anything novel or complex.
Wen was the last time you actually wrote something production level yourself?
deleted by creator
I’m not pro AI or anti AI. I am anti big tech though, which makes the discussion more complicated.
Regarding escalation, a non coding team lead isn’t a dev. A CTO isn’t a dev. A software architect isn’t a dev. A software developer is a dev. That’s not an escalation, it’s a fact.
Just because you lead a team of devs, doesn’t mean you are a software developer, you could’ve gone to business school, never written a line of code and just started leading a team of software developers because you learned “how to lead”. And there are different kinds of team leads, those that get their hands dirty and those that don’t.
So no, being a CTO, CEO, or whatever C you want to put in front of your title doesn’t make you “far exceed” any qualification. I actually think that kind of thinking is the problem workers are underpaid: people who lead actually often exceedingly overestimate their abilities in the craft they lead. “I lead a team of athletes, that means I’m a good athlete”. Do you understand how crazy that sounds?
deleted by creator