If builders built buildings the way programmers write programs, then the first woodpecker that came along would destroy civilization.
~ Gerald Weinberg (born: 1933-10-27 age: 79) Weinberg’s Second Law
Never ascribe to malice, that which can be explained by incompetence.
~ Napoléon Bonaparte (born: 1769-08-15 died: 1821-05-05 at age: 51)
|Blog To discuss Unmaintainable code||Ambiguity||Philosophy|
|General Principles||Testing||The Shoemaker Has No Shoes|
|Naming||Choice of Language||Contributors|
|Camouflage||Dealing With Others||Operation Termite|
|Documentation||Roll Your Own||Feedback|
|Program Design||Tricks In Offbeat Languages||Links|
|Coding Obfuscation||Miscellaneous Techniques|
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.
I would like to remind you this essay is copyrighted material. It is illegal to repost it without permission. I will usually give you that permission if you translate the essay into another language, and if you provide a link back to the English-language original. I do this for three reasons.
Please report any copyright violations.
|recommend book⇒AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis|
|by||William J. Brown, Raphael C. Malveau, Hays W. (Skip) McCormick, Thomas J. Mowbray||978-0-471-19713-3||paperback|
|This is an amusing book that looks at what goes wrong in software development.|
|Greyed out stores probably do not have the item in stock. Try looking for it with a bookfinder.|
available on the web at:
optional Replicator mirror
Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : . If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, especially when sending an ad-hominem attack, a rant composed mainly of obscenities or a death threat, please quote the offending passage and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. I can’t very well fix erroneous or ambiguous text if I can’t find it.
Your face IP:[188.8.131.52]
|Feedback||You are visitor number 2,470,764.|