Cross posted from: https://lemm.ee/post/35627632
this post was submitted on 27 Jun 2024
986 points (98.1% liked)
Programmer Humor
19623 readers
507 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I want - and think will happen - 95% of jobs to be automated eventually. But even in the transition period, where some jobs are automated and some aren't, universal basic income can be a tool to make it livable for all in the transition period.
30% of jobs are going if self driving is achieved. Low pay jobs are here to stay for a while as they're too expensive to automate. The current LLM stuff seems to obsolete low productivity people but still need the skilled writers or programmers to come up with new stuff or do the correct detail work the LLM sucks at.
Some management is going to royally screw up by firing junior programmers since the senior programmers can get all the work done with the help of copilot
But they'll forget that they will in future need new senior programmers to herd the LLMs
This just happened on the team I was on. I'm getting ready to interview for mid-level and senior SWE roles, but was let go from my most recent role a month and a half ago.
My workplace which now uses scaled agile used to be waterfall. We have an enormous system to take care of and there's loads of specialised knowledge, so we were pretty well siloed
So obviously when the sales people sold agile to the organisation they also sold the idea that a programmer is a programmer, designer a designer, tester a tester; no need for specialists, so in 2015 they spun up 50-odd agile teams in about six trains, one for each major system (where the used to be seven silos in one of those systems) grabbed one senior designer and programmer from each major project to put in an "expert" team
And told the rest of us we were working on the whole of our giant system. Where we had trouble understanding how part of it worked, we could talk to one of the experts
Now nine years later those experts have mostly retired, we have lost so much institutional knowledge and if someone runs into a wall you need to hope that someone wrote a knowledge transfer document or a wiki for that bit of the system