I had an interesting conversation today about coding standards, it started with a document How to write unmaintainable code. One of my collegues sent this out after reading slash-dot. It reminded me of, perhaps a more cynical version, of How to get your abstract rejected.
How much of this is tongue in cheek and how much understanding of the natural processes involved is there. Quoting statements like:
Let's face it, you and I and everyone else are going to write crap code anyway, so it may as well be cheap and simple crap code that you understand and can afford to throw away rather than complicated and expensive crap code. (The fact that 90% of the code written by 90% of developers is crap is a corollary of Sturgeon's law that 90% of everything is crap.)