3 ms·
Which is great and awesome. I was the same way. But what unfortunately happens is your output and productivity from this becomes the norm/standard. Everyone abo
by jrs235 10y ago
Which is great and awesome. I was the same way. But what unfortunately happens is your output and productivity from this becomes the norm/standard. Everyone above needs to know they can't and shouldn't calculate not expect this amount of output. Consider it a temporary bonus and never rely or make plans assuming it. That's the difficult thing for everyone above to do. They want to appear to be the hero and they don't want to say no. As a manager or leader, make sure your folks never put in more than 45 hours a week for planned out work. 40 or 35 would be better. Once they got 40 hours for the week or 80 for the two week pay period have them learn a new skill, train them on something else, or tell them to stay home.
- ydt 10y agoI just started a new gig at a place that enforces a 35-hour work week. I get just as much done as I did working 40+ hours, but I'm way happier and just generally more relaxed. It's really amazing what walking out of the office at 11:30 every Friday will do for your mental health.
- mythrwy 10y agoIn my experience, 30-35 hours a week of "real" programming (not meetings/ water cooler chat etc.) is about what I can do sustainability without getting squirrely. I've done a whole lot more for periods of course but pay for it later and can't keep pace week after week without it really taking a toll. My mental state and relationships and personal life suffer. I become generally unhappy. Not to mention my hands and wrists. Burnout is the end and I've discovered in sum it's a loss to push more. If more is expected over time I see it as a company that has no problem eating it's capital and it isn't for me. Other people might be tougher, IDK. But all I can keep is a solid 30-35 hours over the long haul without burning out.