1622
Bernie Sanders says that if AI makes us so productive, we should get a 4-day work week
(techcrunch.com)
this post was submitted on 25 Jun 2025
1622 points (99.4% liked)
Work Reform
12891 readers
4 users here now
A place to discuss positive changes that can make work more equitable, and to vent about current practices. We are NOT against work; we just want the fruits of our labor to be recognized better.
Our Philosophies:
- All workers must be paid a living wage for their labor.
- Income inequality is the main cause of lower living standards.
- Workers must join together and fight back for what is rightfully theirs.
- We must not be divided and conquered. Workers gain the most when they focus on unifying issues.
Our Goals
- Higher wages for underpaid workers.
- Better worker representation, including but not limited to unions.
- Better and fewer working hours.
- Stimulating a massive wave of worker organizing in the United States and beyond.
- Organizing and supporting political causes and campaigns that put workers first.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Does anyone here actually see productivity improvements to their roles from using AI?
I'm a telecoms engineer and I see limited use cases in my role for AI. If I need to process data then I need something that can do math reliably. For document generation I can only reliably get it to build out a structure and even then I've more than likely got an existing document the I can use as a structure template.
Network design, system specification and project engineering are all so specific to the use case and have so few examples provided in public data sets that anything AI outputs is usually nonsense.
Am I missing some use cases here?
Also, if you do see productivity improvements from AI, why would you tell your employer? They want a 5 day working week but they know what they expect to be achieved in that week, so that's what they get.
I do. Part of my job involves writing code and I often don't even know where to start. When I get the first draft I'll know which documentation to read, and then I make it actually work. Even when the LLM fails completely, writing its prompt serves as a rubber duck.
So do you frame the problem to the LLM, get it to spit out an example piece of code and then run through that initial attempt to get an idea of how to approach the problem? Kind of like prototyping the problem?
I take it you find that more efficient than traditional code planning methods? Or do you then start building flow charts/pseudo code from that prototype and confirm the logic to build more readable or efficient code?
Yes. Maybe? I don't know traditional code planning methods. I guess?