in reply to Module of the Week...
Additionally, you could write a review of a module and have the author review it to make sure you understood the intent and scope. I'd love to read reviews of my modules, but many of them have design considerations that aren't necessarily always obvious at first glance. For example, DBM::Deep is meant to be concurrently accessible, but most people use it in a single-process mode so they wonder why there's all this work in there about coordination. :-)
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?