I never wrote automated tests either until recently

This is another practice that seems like a great idea, but I'm just too lazy to force myself to do it. Some day, I vow, I will write test suites for my code. It's just so hard to do when the code I write is usually used by 1 user: myself... [I know, excuses excuses]

the idea really is that running the module wont actually do anything, because that means your code is correct

Indeed, this makes me think of using strict. It's not there for when things go right, it's there for when things go wrong. And of course, since I'm such a big fan of strict, it makes a hypocrite out of me when I say "I've never had a problem with unsafe hashes." I guess I'll just have to live in this state of limbo until I get my act together. 8^)