Tuesday, June 16, 2020
Errors are inevitable. As engineering teams scale and build out their applications, the collection of software errors grows in parallel. We all know that errors are bad, but have you ever considered that not all bugs are worth fixing? The concept of racking up errors for the sake of fast-paced development is referred to as technical debt. So how do you manage your technical debt, protect valuable time at work, and help reduce costs? In this session, James Smith, Co-founder & CEO of Bugsnag, will walk you through hacks and tricks that involve establishing:
1) a common language for discussion between engineering, product, QA, release management, and observability teams
2) a method to measure error impact and application health via stability scores
This talk explains how a data-driven approach provides a unified answer to the age-old question: Do we fix bugs or build new features?