Register to build your agenda.

OPEN TALK: The Unseen Costs of Observability: The Need for Continuous Code Improvement

Cory Virok
Rollbar, CTO, Co-founder

Cory is the CTO and Co-founder of Rollbar, the leading SF-based continuous code improvement platform. He is an experienced technical leader, who is passionate about innovation and creating world class teams and products. His expertise lies in engineering leadership, scalability and performance, software architecture, rapid iteration and AB testing. Prior to founding Rollbar with Brian Rue in 2012, Cory served as the Director of Engineering at Lumos Labs and Lolapps. Cory earned a BS in Computer Science from the Rochester Institute of Technology.

We’re quickly becoming better at building software. The increased adoption of microservices architectures and the move to open source are evidence of this. But, we’re not really that much better at fixing it. Finding and remediating bugs is a drain on developers’ time and productivity. We’re reliant on tools that tell us about the stability of our infrastructures. But with more lines of code being written today than the day before, it’s not enough. Teams are getting too much noise and false signals, creating alert fatigue. Developers spend too long investigating issues, struggle to prioritize what needs fixing, and become less productive.

How we build, test, deploy, and release has become more complex, so finding the root cause of errors has become harder. More contextual information is needed to quickly pinpoint where it’s occurring and better error signals can help reduce the noise by grouping together similar root causes which, in turn, alleviates alert fatigue. Plus, bugs should get resolved before users complain, which is still the top way companies find out about bugs despite all the tools they have in place.

And all of this is happening as companies embrace faster deployment models like CI/CD. It’s why the shift left movement is happening, to move testing earlier in the process to catch issues earlier. But what if you could shorten testing cycles and still catch errors before users do?

In this session, you’ll learn:

* Why developers need to be focused on continuously improving code, and not just observability
* How to boost developer productivity by spending less time debugging
* How to catch errors before users report them