3 ms·

I think the devops-inspired idea of engineers owning what they deploy has become fairly popular, for better or for worse.

• vizzier 2y ago
  For my own part, this wasn't a huge team. We had the knowledge of if the issue was application/software based but would pass back to ops if it was hardware/OS related. One possible bonus, being on call operating your own software also gives you a solid incentive to not wake yourself up in the morning by writing bad code, and fixing those issues that do arise quickly.
  • Viliam1234 2y ago
    > being on call operating your own software also gives you a solid incentive to not wake yourself up in the morning by writing bad code Unfortunately, my software interacts over network with software written by other people; if something goes wrong at 3 AM the users don't know which part caused the problem, so they wake up a random person.
    • fragmede 2y ago
      if your pagerduty/equivalent is doing that, something has gone very wrong at your company
    • sgarland 2y ago
      That’s an observability problem, not an on-call problem.
  • deleted 2y ago
    [deleted]