CivicActions

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!.

I recently made a list of a whole bunch of modules I was interested in, and wanted to gain a quick overview of how they followed Drupal's coding standards. While this is obviously only one metric and there are many others possible (issue queue length, manual code review, simpletests etc), it is a useful and simple way to to get started.

All the talk about coding standards is *mostly* geared towards the professional software developers, those of us who work on large projects with a team of others, and who do that every day. If you're someone who is just willing to dig in and contribute, please continue to do so, feel free to read this article, but it's not really for you.

But let's say you're a programmer. You write great code, that does a lot of good stuff! If you're on the Drupal project, you've probably submitted several patches and even contributed a few modules.