> Code spitters are cooked, let's be honest here and accept the fate so everyone can move on.
I'm guessing "code spitters" here means people who consider their job to be manually writing code based on requirements produced by others.
Personally, I think the role of "developer" has already expanded way beyond that. If you're a technology expert who understand what is and is not possible to build, how it can be built, how to prompt that thing into existence, verify that the implementation is good, then get that implementation safely into production, you're not "cooked" at all.
There is absolutely no place for PM. I say this as someone who has been in PM leadership and built product orgs several times over the last 20 years.
I'm not saying we're surely all doomed here, but there are going to be a lot of changes that none of us can imagine every aspect of, and they are going to happen at a surprising speed, and there are a vast number of cascading impacts that people aren't thinking much about.
eg. if you're in the trades, yes you're safer than a knowledge worker for now, but if all the knowledge workers get wiped out you're both going to have vastly decreased demand for your work (far less individuals will have the disposable income to hire you, companies will have less need for facilities to house employees, so you'll also see a retrenchment on the corporate side) and you'll start getting a labor supply glut as the knowledge workers all desperately attempt to retrain for the 'safe' jobs. And this is just the short term problem, without getting into the robotics threat.
If we don't get ahead of this problem politically (spoiler alert: we won't, at least in the US, it is unclear if we even have a functioning democracy), things are going to get very messy for virtually everyone who relies on labor income.
Is this just domain dependent?
jbv9901•27m ago
gopher2000•23m ago