3 ms·
The corollary here is that if nobody knows when you're working, people will always expect you to work. That whole work/life balance thing depends on having clea
by ocdtrekkie 8y ago
The corollary here is that if nobody knows when you're working, people will always expect you to work. That whole work/life balance thing depends on having clearly denoted "working time" and "not working time".
- eckza 8y agoFull-time remote worker. We solve work-life and burnout problems at my organization by having set hours and hard stops at the end of the day. What you lose in having a fairly rigid schedule, you more than gain back by not having to carry around that “always on” feeling.
- deleted 8y ago[deleted]
- bmelton 8y agoAlso full-time remote worker. We solve the problem by letting people know when you will and won't be available. It can be super informal (e.g. "Hey guys, gonna be out of pocket this afternoon") or entered into a shared calendar. I agree with you (and OP) that there has to be some visibility into what work is going to be done when, and there are lots of ways to solve it, that said, I'm sympathetic to the notion that "I don't care how or when you work, as long as the work gets done." I'm a big fan of measuring developers more by the velocity of their Jira queues and commit history than how often they're available to be bothered with non-coding stuff.
- jfaat 8y agoI guess, but even as an on-site employee if production breaks because of me and I’m not in the office, I’ll still get pinged 10/10 times