I found this thought funny. A few years ago everyone was all learn to code so you don’t lose your job! Now there wont be any programming jobs in 10 years. But we will need a lot of manual labor still.
I found this thought funny. A few years ago everyone was all learn to code so you don’t lose your job! Now there wont be any programming jobs in 10 years. But we will need a lot of manual labor still.
Until they notice that cleaning up after failed AI-written code is more expensive than writing working code from the start. Which is already happening for some companies.
Yes. We’re just getting there. Three years ago, there wasn’t much hiring of junior developers, and it takes about three years for a junior to grow into a senior.
It also takes 3-5 years for stupid code choices to hurt in ways that affect a businesses bottom line.
These two factors should boil over each-other nicely in the near future.
We might have vastly different definitions what is a senior then, or you’re peaking at the Donner-Kebab curve.
I’m referring to the usual definition for the job title, “Senior Developer”. It’s also a pretty good bare minimum skill definition needed to not constantly make costly mistakes.
I didn’t set the industry wide definition, I am using it.
If you’re angry with the lack of titles that reflect real seniority, join a union, or start one!
Why are you pushing emotions at me? Don’t do it.
Even google’s Ai summary slop says that industry standard is 5-10 years, not 3.