See Continuous Code Improvement in Action. Join Rollbar's live product demo!
February 17th, 2021 • By Brian Rue
When Cory Virok and I started Rollbar in 2012, we knew something was lacking in how software was being built. Developers continue to get better everyday at building applications — the widespread adoption of microservices architectures and open source are evidence of this. But, we realized something was still holding us back. And that was how we track and fix bugs.
We both personally felt the pain of spending hours, days, or even weeks investigating issues, combing through logs, to not just figure out how to fix a bug, but to figure out what the bug was. We had application performance monitoring (APM) tools but they only told us the health of our system and infrastructure. The rise of observability is helpful to gain that systematic insight as software becomes more complex. But we didn’t need to understand the health of our systems, we needed to know where our code was broken.
I knew we weren’t the only developers lacking that insight, and I know that pain is still felt in companies, large and small, today. That’s why I’m excited to share our first “State of Software Code Report” that provides insights into the current state of how developers are building software and dealing with the inevitability of bugs and errors.
We surveyed nearly 1,000 developers across the U.S. to find out and uncover key trends and insights, including:
Whether you’re a business leader, an engineering manager, a seasoned developer or in your first developer role, I hope that you’ll find this report useful.