An example I have from work is: We all have the idea that we're working 40 hours a week, on Monday to Friday, averaged across two weeks. This sets the normal pa

An example I have from work is: We all have the idea that we're working 40 hours a week, on Monday to Friday, averaged across two weeks. This sets the normal pace, but I have no problem pulling one or two 12 hours days to put out some massive production fires. It just has to be clear: This means at least 1 day of me not working, usually - if you add in overtime rates - much rather 2. Weekend work is handled in a similar way. 3-4 hours on a weekend are 1 weekday off. If a company respects this and cooperates this way, I'm perfectly fine pulling long hours if necessary, or weekend work if the criticality explains it. But at the same time, if you start micro-managing my hours and start being picky if I organize my hours on a day around some long-running tasks I just need to wait for... I mean be happy I'm doing laundry off the clock or counting reduced time while the archive system is shoveling data towards servers, which requires minimal monitoring. And I have a phone notification setup if it does something weird.