You still had to hire people to do work and tech was good enough to help them out. As tech advanced, people started trusting what the systems said even if blatantly wrong and people started loosing work.
It is probably a safe case that most tech revolutions reduced the number of needed employees for most things. But even then, it would be great if this would provide evidence of that!
Notably, it isn't like people strongly missed this work! Yes, there are fewer secretaries. But there aren't none, and the ones that were responsible for being a scribe to bad bosses almost certainly don't miss that work.
Anyone who has ever worked a physical labor job will be rolling their eyes at this.
There are more dimensions to labor than the number of hours worked. Imagine doing a construction job without power tools or searching through folders of documents instead of using the search function on your computer. Labor saving devices are everywhere and they’ve reduced the amount of labor required during the workday by a huge amount.
EDIT: I guess I wasn’t clear because the replies are still focusing on hours. The point I’m trying to make is labor isn’t only measured in hours. An 8 hour workday of writing code, checking Slack, and sending emails is vastly easier than 8 hours of construction work in terms of physical labor. If you can only see “labor” as number of hours worked, you probably haven’t had a difficult manual labor job ever.
Number of hours worked has actually been trending down for a very long time.
It probably feels that way to someone who got comfortable doing their job the old way wishes the world could go back to when they had it all comfortably figured out.
If this does happen, it’s a second order effect from reducing the barrier to entry. Now that anyone can make some code with enough prompts, it’s no longer impressive to be able to make simple apps. You have to bring something different and better to the table. Good developers still do this on top of what AI can do by itself, but I also think there were a lot of relatively easy programming jobs where you didn’t have to be particularly good at anything. You had to know how to follow the rules, get easy tickets from the tracker, make enough changes that you could call it done, and then go on through the dog and pony show of getting the PR approved and getting those story points to count for your standup report. Repeat 5 days per week.
Every mid-size and larger company I worked for had a collection of developers like this: Not really trustworthy or skilled enough to handle big tickets, but you could assign all the loose ends and easy tickets to them. They’d get done eventually while the other devs could focus on bigger efforts.
Now, it’s hard to justify having a lot of those easy ticket solver developers around. An experienced developer can take 10 easy tickets, use their codebase knowledge to write targeted prompts with Opus or Fable, quickly review the code, and have all the easy work done in an afternoon. Then back to the hard tickets.
If you were one of those developers coasting on the easy work, this revolution probably feels like it increased expectations unfairly. If you were one of those devs doing the hard work, you have another tool to use but you’re still grinding away at the hard problems with an extra tool to make some of the parts easier.
something less positive i noticed, in offices, is that technology is not there to help you, management get sold something shiny to replace the old and dusty, the supplier assembles a bad team, implement crappy network, install new web stuff that is sluggish and requires new machines, and employees are left holding the bag. the new tech is often way more limited than the old junk (feature dropped, bad ergonomics for prolonged work, no more scripting options), the integrations are lacking, the people are not trained .. it's often a slow mess full of redundant steps and missed opportunities.
dude250711•1h ago