4 ms·
On call incidents shouldn't be routine. A rotation spreads responsibility across the team. Ultimately, someone has to be responsible for incidents and it aligns
by dyeje 5y ago
On call incidents shouldn't be routine. A rotation spreads responsibility across the team. Ultimately, someone has to be responsible for incidents and it aligns incentives best for it to be the engineers who maintain the code.
- manuelabeledo 5y ago> it aligns incentives best for it to be the engineers who maintain the code. How many at a time? It has to be two or more, otherwise anyone could push changes to production at any time, without supervision.
- dyeje 5y agoI recommend one per team. You want somebody who is knowledgeable on the specifics of any part of the system that could break. I don't think having more than 1 is a requirement though, if we're talking about small companies. As long as there is a "break glass in case of emergency" way to push to production that is auditable.
- manuelabeledo 5y agoDo you trust every single dev to push the right workaround?