Chris O’Dell - Monzo
Development of a feature doesn’t stop at deployment, your involvement continues for the lifetime of the product. If you want great power to control the choice of tooling and approaches, then you accept the great responsibility of ensuring it works, and remains working, in Production.
In this talk I’ll explore the topic of Developers supporting their own features in Production. I’ll cover the benefits of this approach, including greater understanding of your product, its usage and performance, and how this data can be fed back to improve your product. I’ll also talk about the downsides of being on-call, combined with the strategies from Ops teams on how to handle these. You’ll come away from this talk feeling empowered to own your own work.
Learning outcomes
Developers have the most context and therefore are the best placed to fix a production issue
There is a lot we can learn from the Ops team for improving on-call
Gracefully handling failure needs to be built into the applications
On call is a mentally challenging task. This must be taken into consideration and the mental health of your stuff must be carefully considered
Audience
Developers, Development Managers, Engineering Leaders. Those already on call or those being considered for it. Sceptics welcome :)
How this enables organisational sensing
It helps organisations make sense of the support requirements of software. This includes building in techniques for managing failure and the people side of being on call.