I started work on the coder module a little over a year ago, as a response to an internal engineering meeting where were discussing Quality Assurance code reviews, and said "we should have a module to do that." At OS/CMS I briefly introduced coder in the Lightning Talks session. While in Barcelona, pre-conference, I gave a Drupal Dojo titled Upgrading your contrib modules to D6? Coder module can help!. At the Barcelona DrupalCon, I presented a talk titled Code Review is not just for Standards (slides here). A team of people have contributed to make coder a better assistant. The 5.x -> 6.x upgrade review has been in progress for almost a year. I wrote the original upgrade review. The entire CivicActions had a session last June, where we wrote finished these rules. webchick and nancyw have done quite of bit of suggesting and testing and a big shout-out to snpower who has CVS rights and is my co-maintainer. Now that 6.x has been released, and the module upgrade season is upon us, the coder upgrade review is being used by many people and helping us upgrade quicker and better. Next week at the Boston DrupalCon, I'm giving another talk titled A Developer's Assistant - Using Coder for Module Developers and Maintainers. While my talk in Barcelona was meant to attract more developers for the coder module itself, this DrupalCon presentation will be similar to the Drupal Dojo session, in that it's geared towards module developers and maintainers. I'll also set aside some time for a group discussion on the future of coder. Please join me, even if you use coder regularly. I hope to offer a few little known secrets and the discussion on the "future of coder" will be invaluable to the future of Drupal and our community.