How to write unmaintainable code

This article by Roedy Green, available here:

http://mindprod.com/unmain.html

ties in nicely with our discussion of naming conventions that started in the "m." thread.

From the title, it is obviously parody, but the article does a great job of pointing out (in a reverse sort of way) the majority of ways you can help ensure your code has a long life. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br> [/sig]

 

[BlindPete]

he he <grin> [sig]<p> Pete<br><a href=mailto:blindpete@mail.com>blindpete@mail.com</a><br><a href= > </a><br>What your mother told you is true! You will go blind! (from moonshine anyway)[/sig]

 

[jonscott8]

My favorite:

Thesaurus Surrogatisation: To break the boredom, use a thesaurus to look up as much alternate vocabulary as possible to refer to the same action, e.g. display, show, present. Vaguely hint there is some subtle difference, where none exists. However, if there are two similar functions that have a crucial difference, always use the same word in describing both functions (e.g. print to mean write to a file, and to a print on a laser, and to display on the screen). Under no circumstances, succumb to demands to write a glossary with the special purpose project vocabulary unambiguously defined. Doing so would be unprofessional breach of the structured design principle of information hiding. [sig]<p>Jon Hawkins<br><a href=mailto: jonscott8@yahoo.com> jonscott8@yahoo.com</a><br><a href= > </a><br>Focus on the solution....Not the problem.[/sig]

 

[TomasDill]

My favorite is 'Do It' ) - specially for VFP [sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]

 

[foxdev]

My favorite is 'Do It'

No lie: I have seen DoIt as both a variable and a procedure name.

I myself am guilty of (unintentionally) using synonyms: show and display in particular. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br> [/sig]

 

[oublie]

Hey this document reads like a training manual for a contractor! - Make it impossible to maintain then the company will call you back and pay you huge sums of money to fix you own code!

Now what was the URL of that Recruitment Agency??...
[sig][/sig]