unmaintainable code : Java Glossary

Introduction

“If builders built buildings the way programmers write programs, then the first woodpecker that came along would destroy civilization.”
~ Weinberg’s Second Law (born: 1933 age: 76)

“Never ascribe to malice, that which can be explained by incompetence.”
~ Napoléon Bonaparte (born: 1769-08-05 died: 1821-05-05 at age: 51)

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. The easiest way to navigate is to hit the next page button at the bottom left of each page.

	recommend book⇒AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis
		paperback	kindle
	ISBN13:	978-0-471-19713-3	B000U5M2EM
	ISBN10:	0-471-19713-0
	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.
abe books.co.uk abe books.ca amazon.co.uk amazon.ca abe books.de chapters.indigo.ca amazon.de abe books.com abe books.fr amazon.com amazon.fr barnes and noble.com abe books.it powells.com iberlibro.com abe books anz