|
|
|
|
|
by metaloha
1988 days ago
|
|
Having a rotating "dev on call" (weekly, maybe) could work well as long as there is good enough telemetry for any problems that might occur that would allow any dev on the list to at least triage problems that arise. Sorry about the length of that last sentence. It would also encourage devs to have an idea of how every section of the product works, not just their specific window into it :) Combine that with enforcing non-work time and it _should_ be cool as long as your company isn't trying to take advantage of you. I don't have Slack installed on my phone because I've learned that any problems with my code are either a) not serious enough to get me to work at 9pm (i.e. it can wait until morning), or b) serious enough to warrant an actual phone call (because let's face it, I could be out in the yard, out grocery shopping, etc. and not able to use a computer and read Slack or email messages conveniently). Startups in particular can sometimes take advantage of employee's willingness to be available 24/7 by expecting _all_ employees to be available 24/7, but that should definitely be voluntary. |
|