2 ms·
Everything you said sounds reasonable. Tasks and hours are related to the specific work at hand, and mitigations are then given, as temporary allowances, to emp
by arthurcolle 6y ago
Everything you said sounds reasonable. Tasks and hours are related to the specific work at hand, and mitigations are then given, as temporary allowances, to employees if extra work is demanded that are outside of "core hours"
I was just trying to highlight that I personally hate "core hours" and that if I'm on a marathon coding session from 9pm to 4am, and I'm intermittently unavailable from some arbitrary time (say 11:15am to 11:50am) and then I get a bunch of messages from bosses saying "where were you??" and I then explain that I was actually writing code, point to some commits and say "see? I did all this stuff" and they say "you are expected to work from 9am to 6pm" it feels like a slap in the face. I think good management should accept that people aren't robots (unless there is an outage, fair enough) and consider people's working preferences in their decisions.
Anyways, I'm sure you have some awesome war stories with deployments/maintenance events. You should share them sometime :D
- murph-almighty 6y agoThere are definitely good reasons to, at minimum, have you _available_ from 9-6; say, for a meeting or to bring a coworker up to speed on what you're working on, but at the same time you don't necessarily need to be pinned to your desktop for the entire period of time to do that. Since remote working started I've taken advantage of that big time by just running errands during the work day but keeping my phone close by in case I get a ping on Slack.