Over a million developers have joined DZone.

Detect Errors Earlier To Improve Code Quality

DZone's Guide to

Detect Errors Earlier To Improve Code Quality

We sat down for a brief interview with James Smith and Chuck Dubuque, executives at Bugsnag, about the state of monitoring in the tech industry.

· Performance Zone ·
Free Resource

Sensu is an open source monitoring event pipeline. Try it today.

Great speaking with James Smith, CEO and Chuck Dubuque, CMO of Bugsnag, a company that provides error monitoring for web, mobile, and server apps to improve the quality of software without developers needing to access logs.

The company is five years old and their mission is to provide visibility when things break to improve the speed and quality of code. Bugsnag highlights crashes, exceptions and failed renders to ensure that every user session ends with a good customer experience. The solution is for cloud-native agile and DevOps environments and focuses more on the engineering and product teams.

Q: How do you see the SDLC evolving?

A: Cloud-native is progressing nicely. A non-cloud waterfall is a "hot potato" between developers and operations. We strive to empower everyone in the SDLC to have visibility from end-to-end. Uptime used to be the golden metric. Today, uptime is "table stakes" and stability has become more important given the number of releases being deployed. We provide alerts throughout the stack.

Image title

Q: What are some use cases you like to highlight?

A: Lyft is always taking beta versions of their application to production. They are using Bugsnag to understand when it's ready with regards to A/B tests or new features. Other companies use us for experimental and phased roll-outs.

Q: What are the most common problems you see among clients today?

A: The pressure to release quickly. There's a lot of fragmentation of client-side devices with mobile and web apps. The environment in which you deploy software is very fragmented. You cannot test every device or the interaction with other apps.

Q: What's the future of development look like?

A: DevOps will have ownership of the full product development lifecycle and the team will take pride in the code that is written. Developers will know they will see their code again which is actually good for professional development since they will take more ownership of the code they write. There will be a beautiful, and short, feedback loop. A lot of languages. Swift reaction to common crashes and uninitialized variables. We'll be able to enforce code quality in real-time and know the prevalence of a bug which may be increasing with program language design. QA will be less manual.

Q: What do developers need to keep in mind to develop better code?

A: Adopt the philosophy of continuous improvement. You will only get better if you care about your craft and strive to improve every day. Software engineers have many ways to measure code quality. Get to understand the tools they are using and learn how you can use them to improve. Get insights into what's going on under the hood.

Q: What do our readers need to know that I haven't asked you?

A: Developers and engineers are used to using logging systems like Splunk and APM (application performance management). However, they are very time-consuming. We provide a daily dashboard of the metrics you care about. You can try the tool free for 14 days. It integrates with languages on the frontend and backend through open source SDKs. A lot of developers begin using Bugsnag on their personal side projects and then bring it into the office.

Sensu: workflow automation for monitoring. Learn more—download the whitepaper.

performance ,bugsnag ,monitoring ,sdlc ,interview

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}