this post was submitted on 28 Jan 2024
1042 points (97.6% liked)

Programmer Humor

19450 readers
268 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

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 26 points 9 months ago (2 children)

I mean honestly for things like tech, the jobs are going away due to these innovations, just piecemeal. Each of these innovations have shaved hours off of projects. Now someone's salary might be the same and they might still have to go into the office 40hrs a week (or be just as productive working from home, go figure) but the actual work they're doing is that much easier than it used to be, they might only have to work 4 hours a day now to accomplish what might have taken 2 days in the past.

Sure, certain companies put more demand on employees than others, and as you mentioned there are still human components to the system that remain untouched by technology, but if the tech world was honest with itself tech employees do far less work now than they did 10-20 years ago, disregarding the general expansion of the tech industry. I'm just talking about individual jobs.

Of course I don't think those employees should be making less. I think if we innovate so much that a person's job disappears we should be able to recognize that that person still deserves to be clothed and fed as if they still had that job.

[–] [email protected] 26 points 9 months ago (1 children)

Yes, except for the fact that the flip side of those is that software, almost by definition, is automating away jobs in other industries.

So when it gets easier / cheaper to write software, other industries will spend an increasing amount on it to replace their workers. That's one of the reasons the software industry has continued to grow, even though it's gotten easier to write.

[–] [email protected] 4 points 9 months ago (1 children)

Sure, but also almost by definition, using tech to replace workers in other industries will reduce the total amount of workers needed for that job as you made the tech presumably to make the job easier or faster. My post was talking about the tech industry just because that was the topic, but as you mention, tech definitely replaces jobs in all sectors.

[–] [email protected] 7 points 9 months ago* (last edited 9 months ago) (1 children)

almost by definition, using tech to replace workers in other industries will reduce the total amount of workers needed for that job

The data on this is actually uncertain. Installing ATM machines to replace bank tellers should have been a slam dunk, but didn't really cut into bank teller total employment.

https://www.aei.org/economics/what-atms-bank-tellers-rise-robots-and-jobs/

Don't get me wrong, the ATM was the first step in a long chain of improvements that still ought to soon make bank tellers obsolete, and the dept of labor predicts 15% lower demand next year.

But even this relatively one-for-one swap of machines for people has taken half a century, so far.

[–] [email protected] 5 points 9 months ago

That goes back to the point I was making earlier. For some reason a bank teller is hired for the same wage for the same hours, but I can almost guarantee you that because of the ATM they spend significantly less of their work day "working" because the ATM was designed to do a significant portion of their job. There certainly is an excuse to keep them around all day, there are some unavoidable tasks that only a human can do and they come up at random times throughout the day, but the ATM has replaced many of the working hours the bank tellers used to have even if the job didn't go away.

[–] [email protected] 11 points 9 months ago

tech employees do far less work now than they did 10-20 years ago

Agreed!

Of course, if we had truly understood the situation 10-20 years ago, we could have admitted that they were primarily being paid to know how to get the thing* to work, and not actually for the hours they spent typing in new code. Hence the rise of "Infrastructure Engineer" and "DevOps Specialist" as titles.

*I omiitted the technical term, for brevity. But to be clear, by 'thing', I mean what professionas typically call the "damned fucking piece of shit webserver, and this fucking bullshit framework".