EclipseCon France: Because you can't fix what you don't know is broken - Automated Error Reporting in Eclipse Mars

It's a well-known fact that fixing bugs during the development of a software product is 25x cheaper than fixing them after the product was shipped to your customers. This is in particular true for platforms like Eclipse with an estimated user base of more that 10.000.000 Java, C/C++, PHP, JavaScript users working with it every day.

Thus, software development teams often rely on a 'ship early, ship often' strategy to learn where their software breaks 'in the field'. But while it is easy to spot problems in a web app, it is many times harder to spot issues if your app runs on a client's desktop or mobile device. The key problem here is that your users only rarely report back all problems they experience. They usually just uninstall the software and disappear with bad feelings about your product...

Eclipse Mars introduced an Automated Error Reporting for the Eclipse IDE that helps collecting problematic situations on the client side and provides committers with the necessary feedback where their code breaks. It's my pleasure to present the error reporting tool but also to look back on 9 months of development and speak about adoption and bug fixing rates and challenges we had to solve to make automated error reporting work for a community that ships more than 65 million lines of code - every year in June.

Join me on Thursday afternoon in the Diamant room (14:00 - 14:35) [1]. I'm quite confident you'll find many interesting insights to talk and think about - and hopefully some of them will find their way into your products. Automated Error Reporting is worth it...



Add new comment