Call us: +32 (0) 3 298 69 98
Email us: info@krimson.be
Call us: +32 (0) 3 298 69 98
Email us: info@krimson.be
This morning I went to the A Developer's Assistant - Using Coder for Module Developers and Maintainers session by Doug Green. The coder module is a handy piece of code that should be in every module developer's toolbox. It's just a normal module (download it, install it, use it) that offers a pretty wide range of code analysis:
This is a very nice feature set that makes my live as module maintainer a lot easier (especially when updating to new core version) and I would recommend any developer to use it.
An interesting experiment that Doug did was to run Coder's style review against "all of Drupal":

which brought up a list of most common code style errors:

A nice feature I didn't check out yet is that the coder module also hooks into Drush (a command line Drupal tool), which probably can streamline coder usage if you're into command line geekyness.
Another interesting thing brought during the Q&A part was that the idea of combining Coder and SimpleTest. That would be very handy to automate Coder's review and maybe even produce some kind of quality metric (which is a hot topic now in the drupal.org redesign efforts).