this post was submitted on 13 Sep 2023
72 points (97.4% liked)
Programming
17313 readers
251 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My developers are only "on call" in the sense that their code supports responders who save lives.
In that context, I maintain the expectation that I might call any of my developers at any time.
That said, I have made that call once ever in the years since I built this team, and it happened to be during business hours anyway.
Officially, I require my team members to take off time to make up for any overtime worked. (Only officially, I guess, since it has not been tested.)
Our flexible work schedule already sets an expectation that someone too tired to work should let their manager know and sleep in and come in later. That has been tested, for various personal reasons. So that would still apply for a late night or early morning incident.
I'm not able to pay an overtime rate, at this time.
I credit my prioritization of graceful rollback for some of the lack of actual on-call calls. But lots of credit is also due to our fantasticly skilled first line responders.