On Tuesday, I went to the regular Chicago Ruby meetup, where Jake Scruggs talked to us about his gem, Metric_Fu. We’ve been thinking a lot about our continuous integration patterns lately, so it was an interesting and relevant presentation for Neoteric.
For the uninitiated, continuous integration is a fancy term for regularly testing and refactoring code (and refactoring essentially means “make leaner and clearer”). Metric_fu is a small piece of software that runs against your code and tells you certain things about it.
For instance, metric_fu reports on:
Percentage of test coverage (how much of your code has tests written for it?)
Code smells (pieces of code that may be leading to problems)
Design pattern practices (is your code going against convention?)
Churn (which files are changed the most over time, making them most vulnerable to bugs)
Best practices (don’t write the code like this, write it like this)
At the end of the day, it’s a machine trying to help you make decisions about human aesthetics, so we’re advised to take the reports with a grain of salt.
But code health and clarity is essential for its stability and future development from collaboration with others. We like the idea of gathering this kind of information, and we’ll soon be implementing metric_fu into our development cycle.
Have a comment or question? Send us a note. It won't be shown here and email isn't required, unless you'd like a