How To Write Unmaintainable code (was: to code or not to code?)

[Mike Cantrell]

Found this on slashdot awhile back:

http://mindprod.com/unmain.html


Regards,
Mike Cantrell



----- Original Message -----
From: "David Sinck" <sinck@owmyeye.ugive.com>
To: <plug-discuss@lists.PLUG.phoenix.az.us>
Sent: Tuesday, July 25, 2000 12:19 PM
Subject: RE: to code or not to code?


>
>
> \_ It's best if you liberally intersperse code with comments, explaining
not
> \_ only what is happening and why, but also why you *didn't* do it some
other
> \_ way.
>
> For a long time I've maintained that I want to find a book of what
> *not* to do...the Tome of Anti Knowledge.
>
> "Don't do a multi-dimensional-mip-map because the computers can't
> support that much memory."
>
> "Don't issue rm -rf /"
>
> and so on.  All the academic papers out there explain how they've got
> cool results.  How many have you seen that explain, "well, this petri
> dish is dead and empty when it should be at least growing."
>
> David
>
> _______________________________________________
> Plug-discuss mailing list  -  Plug-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss