Homage to coding guidelines authors

Code is read much more often than it is written. Guidelines are intended to improve the readability of code and make it consistent across the wide spectrum code. As Python's PEP 20 says, "Readability counts". While we all know how important styleguides are for writing code. We never take time to write one. We always refer to an existing guideline and maybe... maybe take the time to write an addendum to it. It's time to say thanks to people that take the time to do that.

First of all, Scott Ambler, thank you for your amazingly complete coding guidelines for Java that I used on numerous projects since 2000 or so. Thank you Douglas Crockford for the JavaScript guidelines. We've move on since then, but these were the first I ever used. Oh Eiffel, yes, thanks for those as well. Then there is puppet, bash, vimscript, ruby, perl, python, html, css, .. so many people to thank.

Nearly everybody is convinced that every style but their own is ugly and unreadable. Leave out the "but their own" and they're probably right...
-- Jerry Coffin

And in the now, thank you Bozhidar Batsov for the excellent styleguide for Clojure. The fact that we forked it, is not that we don't like it, but proof that we use it!