Hi everyone, I set up my fork of Geode with CodeClimate to see if the tool might get us interesting information. You can see the results here <https://codeclimate.com/github/pivotal-amurmann/geode>
The current configuration of CodeClimate uses PMD (https://pmd.github.io/) with the *Basic, Code Size* and *Coupling* rulesets <https://pmd.github.io/pmd-5.8.1/pmd-java/rules/index.html>. Geode has six *critical* issues <https://codeclimate.com/github/pivotal-amurmann/geode/issues?severity=critical> that we should take a look at as soon as possible. I have not yet identified if these are false positives or not. The biggest value we can get out of this tool right now seems to be the *churn vs. code quality* <https://codeclimate.com/github/pivotal-amurmann/geode/trends/churn> graph. We have 65,000+ issues in total. It's not feasible to address all of these. We can however use the *churn vs. code quality* graph to guide our decisions in what to refactor. Code that changes frequently and is of poor quality is a prime refactoring target. Michael Feathers explains this much better than I can: https://www.stickyminds.com/article/getting-empirical-about-refactoring Do you find this analysis interesting? Are there any rules in the PMD tool you'd like to see added or removed? Thanks for all feedback and input on this!
