3 ms·
Yes, I've thought the same thing. Wasn't 40 hours mainly about factories and coal mines --- though 40 hours in a mine would also be exhausting. But I think you
by combatentropy 9y ago
Yes, I've thought the same thing. Wasn't 40 hours mainly about factories and coal mines --- though 40 hours in a mine would also be exhausting. But I think you meant something like a barista.
To my bosses and other non-programmers, I try to describe programming as doing math problems all day. I wonder what the history of hours is for clerks, architects, and other jobs more like ours.
I feel like I would be less tired if I just worked trouble tickets all day. Actually, writing a program too would be easier if that's all I did. Instead, I switch among writing a few different programs, working tickets, and the normal bureaucracy of emails, meetings, required training, etc.
- JBlue42 9y agoBeing a barista can be exhausting at fast-paced place. Not as hard or deadly as coal mining, of course. I work with architects. They work as much as they want to but are paid salary. The minority walk out of the office after their 8 hours is up but many work late into the night and on weekends. They say it's their "industry standard" but, from my observations, it's a) lack of boundaries and b) poor project/time management. Not to mention the amount of time studying to take their many exams to become licensed.