The team behind Hipchat, the popular group chat, file sharing, video chat, and screen-sharing application used by millions of people around the world, and their counterparts on the Sourcetree team, are two teams actively using BugSplat for crash reporting at Atlassian.
In the below interview we talk to Dustin Henry of Hipchat about crash reporting, BugSplat, and taking over the world!
BugSplat: Hi Dustin, thanks for taking the time to speak with us today!
Dustin: No problem at all. My pleasure!
BugSplat: What factors contributed to your decision to integrate BugSplat?
Dustin: When searching for a Windows crash-reporting system, BugSplat was the clear winner, given your feature set, ease of implementation into Hipchat, and the fact that you were already ahead of the curve with a Jira integration for tracking defects beyond the initial crash report.
BugSplat: How has Hipchat benefited from crash reporting?
Dustin: Crash reporting is an essential part of any enterprise-level software application, especially with a large daily user base composed of users with a variety of hardware configurations. BugSplat has allowed Hipchat to not only find and solve possible problems in our code base but also in those of various third-party libraries we use.
BugSplat: How does your team use BugSplat on a day-to-day basis?
Dustin: We use BugSplat on a daily basis to ensure the health of Hipchat and to verify that every new version maintains a high level of quality.
BugSplat: In your opinion, what do teams risk by not prioritizing crash reporting?
Dustin: Crashes are a fact of software. Even with great developers and extensive QA, it’s impossible to plan for every scenario. With crash reporting, you have a real-time look into the health of your product and the ability to really dig deep into what the possible problems could be.
BugSplat: Do you and your team have a favorite way to celebrate after big wins?
Dustin: Same thing we do every night, Pinky . . . try to take over the world.