I recently spoke to Nick Rockwell, CTO at The New York Times (a Sentry customer), and Yonas Beshawred of Stackshare about simple solutions, React, and going serverless. Take a listen or read on for the highlights. Because why would we even bother with the lowlights?

With Sentry 9, our goal is to increase the relevance of the information you see in Sentry in order to speed up your time to resolution, while also making the process of fixing application issues less annoying for everyone involved. How are we accomplishing this? We’ve increased our focus on Ownership of issues: expanding your ability to control who owns what in your Projects, while expanding the power of teams and individuals to take action with that ownership.

We recently raised an additional $16 million in funding from our partners at NEA and Accel. What are we going to do with these additional funds? Great question! For a long time Sentry has had a rigid, singular focus: given an application error, discover everything a developer needs to know about it and inform the team as quickly as possible.

Errors. We all cause them all the time, which can make it difficult to figure out the person or team who should be responsible for fixing individual issues. Time that could be spent resolving an issue is instead spent tracking down who should be handling it and what it’s even about. This is a waste. It balloons time to resolution, often from minutes to hours or sometimes even days.