Static Code Analysis
We all know that finding bugs as soon as possible saves time and money. Static code analysis is one of the best ways of finding bugs early, and yet very few development teams have built it into their process. To us, that's analogous to doctors not washing their hands.
Some people believe that static code analysis is just for finding stylistic issues, not real bugs. Not any more. Static analysis can't find every bug in your code, and it can't check that you implemented what the customer actually wanted. But there is a class of bugs that can be found by static analysis, so why not knock those ones out first?
Another objection to static analysis is that it gives too many false positives. Many people have the experience of trying out a code analyzer on their existing code base, only to have it report tens of thousands of violations. Usually, that's when the static code analyzer gets disabled.
That's why Enerjy analyzes your code first, then makes some helpful suggestions about which rules to enable and which to turn off before you ever see those violations. It also let's you "baseline" those rules in your existing code that fire often. That means Enerjy will ignore any of those rules in pre-existing code, but will continue to report them for any new code that you write. So, you can avoid getting bogged down in thousands of rule violations, but still have those rules applied to new code that you write.
Finally, many people object to having to change the way they work, by introducing a new step in the development process. That is why we made Enerjy work in the background, automatically analyzing code without you having to do anything. And it's well integrated with the Eclipse environment so that violations show up in the problem pane, where you would expect to find them.
Read more about static code analysis and coding standards on the Enerjy Blog.
Or, if you're ready to try Enerjy, you can download it directly from within Eclipse. Find out how here.