How to Write Unmaintainable Code
Most programmers have, at some point, had to maintain someone else’s code. And it usually sucks. A lot. Maybe there are no comments at all, or if there are comments they’re not helpful (e.g. i++; //increase i by 1). Perhaps that why this “guide” to writing unmaintainable code made me laugh out loud.
If, for example, you were writing an airline reservation system, make sure there are at least 25 places in the code that need to be modified if you were to add another airline. Never document where they are. People who come after you have no business modifying your code without thoroughly understanding every line of it.
I’m not sure how old this is, but it’s a goodie.