HI version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
50% Positive
Analyzed from 331 words in the discussion.
Trending Topics
#hours#hard#managers#realistic#expect#knowledge#https#tasks#hardest#problems

Discussion (10 Comments)Read Original on HackerNews
Software engineers are probably already familiar with the feeling of burnout from thinking too hard. The reality is very few people can work on the hardest problems they’re capable of for 8 hours a day.
Writing routine Python code for some system you know well is not that mentally taxing. Managing an agent that rapidly finishes tasks but needs careful review and big-picture planning is much more exhausting, and has higher returns on intelligence and deep careful thought.
I think this points towards the opposite conclusion of the OP. It’s not realistic to expect 8 hours of hard work out of a knowledge worker. Remote work naturally allows this transition, as employees can work a bit less but still overachieve with AI.
(I hate AI. Just observing the world we live in)
It wasn’t really realistic to expect hard physical labor for 70 hours a week, and yet in the 1800s before unions were established to negotiate workers rights, that’s exactly what we had.
What on earth makes you think non unionized IT workers aren’t going to be pushed to their breaking point and then pushed further? If AI truly starts eating all the knowledge work, there will be an endless supply of people lining up to work themselves to death.
Rinse, repeat.
[1] https://www.refolk.ai/blog/coinbase-ai-native-engineering-ma...