Introduction

“Never ascribe to malice, that which can be explained by incompetence.”
~ Napoléon Bonaparte

In the interests of creating employment opportunities in the Java programming field, I am passing on these tips from the masters on how to write code that is so difficult to maintain, that the people who come after you will take years to make even the simplest changes. Further, if you follow all these rules religiously, you will even guarantee yourself a lifetime of employment, since no one but you has a hope in hell of maintaining the code. Then again, if you followed all these rules religiously, even you wouldn’t be able to maintain the code!

You don’t want to overdo this. Your code should not look hopelessly unmaintainable, just be that way. Otherwise it stands the risk of being rewritten or refactored.

This giant essay has been split into sections to make it faster to load.

	recommend book⇒AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
		paperback
	ISBN10:	0-471-19713-0
	ISBN13:	978-0-471-19713-3
	publisher:	John Wiley & Sons
	published:	1998-03-20
	by:	William J. Brown, Raphael C. Malveau, Hays W. "Skip" McCormick, Thomas J. Mowbray
This is an amusing book that looks at what goes wrong in software development.
amazon.ca amazon.com chapters.indigo.ca powells.com amazon.fr barnesandnoble.com amazon.de amazon.co.uk