A few years ago I found an article pointing out how spammers had figured out how to abuse some code I wrote back in 2001 or so. I’d put it on the list to fix and even started a blog post so that I could take my lumps publicly.

Now I’ve rediscovered that draft post…and that I never fixed the bad code it had fingered. Worse, I’m no longer in a position to change the code.

Along similar lines, I’ve been told that a database driven DHCP config file generator that I wrote back in the late 1990s is still in use, and still suffers bugs due to my failure to sanitize MAC addresses that, being entered by humans, sometimes have errors.

I’ve written bad code since then and will write more bad code still, but as my participation in open source projects has increased, I’ve enjoyed the benefit of community examples and criticism. My work now is better for it.

I can’t help but like microformats, and part of that comes from the dogmatic principles that drive them. Among those is the notion that none of us should attempt to create a format out of whole cloth. Here’s how they explain it:

Under the title of “Propose a Microformat” they tell us: “Actually, DON’T!!!”

ask yourself: “are there any well established, interoperably implemented standards we can look at which address this problem?”

Why? The dogma here is to “pave the cowpaths:”

It’s quite possible [...] that you’ll find someone else who has dealt with the problem you’re addressing. Perhaps even solved it. Do your best to open a dialog with others who have encountered the same problem. We don’t want to build walls between competing communities — we want people to work together to develop a good solution which will cover the majority of cases.

Now think about this in the context of libraries. Think about it in terms of our acquisitions workflow, think about it in terms of our online catalogs. Break down the walls that divide libraries from the rest of the world, look for and embrace larger standards, and benefit from the community of work that already supports them.

microformat, dogma, lessons, software development, standards, interoperability