Earlier quoted context omitted.
There are three takes that I think are not depressing: * Being excited to be able to write the pieces of code they want, and not others. When you sit down to write code, you do not do everything from scratch, you lean on libraries, compilers, etc. Take the most annoying boilerplate bit of code you have to write now - would you be happy if a new language/framework popped up that eliminated it? * Being excited to be ab…
Those are all good outcomes, up to a point. But if this stuff works TOO well, most or maybe all of us will have to start looking at other career options. Whatever autonomy you think you have in deciding what the AI does, that can ultimately be trained as well, and it will be the more people use it. I personally don't like it when others who don't know how to code are able to get results using AI. I spent many years o…
Those jobs still exist, but by large are either very niche or work using that tech in some way.
It is not wrong to feel down about the risk of so much time, training, etc rapidly losing value. But it also isn't wrong that change isn't bad, and sometimes that includes adjusting how we use our skills and/or developing new ones. Nobody gets to be elite forever, they will be replaced and become common or unneeded eventually. So it's probably more helpful for yourself and those that may want to rely on you to be forward-thinking rather than complaining. Doesn't mean you have to become pro-AI, but may be helpful to be pragmatic and work where it can't.
As to work supply... I figure that will always be a problem as long as money is the main point of work. If people could just work where they specialize without so much concern for issues like not starving, maybe it would be a different. I dunno.