Not likely to break (Rank 10)

Pentaho Reporting has been ranked #10 in Enerjy’s analysis of open source projects that are not likely to break.

Enerjy performs some static code analysis on the source code and computes several metrics on how well the software is maintained. Thanks to our paranoid programming, which assumes that the users of the code (in most cases: I) are way to stupid to code correctly all the time. Therefore we write the code in a way that breaks early and hard – including strict assertations, strong typing and explict checks for Null-References as soon as we receive parameters on public or protected methods instead of happily assuming that the humans never produce bugs and accepting everything first (hoping that things will continue to go well) and acting surprised if – no: when – later in the process the assumptions have been proven wrong.

Always protect yourself when coding – you never know what diseases you might catch otherwise.

This entry was posted in Development on by .
Thomas

About Thomas

After working as all-hands guy and lead developer on Pentaho Reporting for over an decade, I have learned a thing or two about report generation, layouting and general BI practices. I have witnessed the remarkable growth of Pentaho Reporting from a small niche product to a enterprise class Business Intelligence product. This blog documents my own perspective on Pentaho Reporting's development process and our our steps towards upcoming releases.