OT: Good Programming Courses Suggestions for technique rather than language

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Thu Sep 3 19:50:11 UTC 2009


On Wed, Aug 26, 2009 at 06:37:54PM -0500, colin davidson wrote:
> Finally, observe the KISS (Keep It Simple, Stupid!) principle and, to
> paraphrase Einstein, make your code as simple as it can be, and no simpler.
> When you have finished writing something (be it a clause, a function or a
> program), ask yourself "Is this code really clever?". If your answer is
> "Yes!", ask yourself "Does it really need to be clever?". If your answer is
> "Yes!", rewrite the damn thing. Unnecessarily clever code is bad code,
> period. Once you get past the meaningless gobblydegook written by computer
> language illiterates who call themselves coders (and practice will almost
> certainly remedy this problem in anyone inherently capable of programming a
> computer), the most common kind of bad code by far is "clever" code.

This is very important.  After all debuging is harder than coding, and
if your code is very clever, then you probably aren't smart enough to
debug it.

-- 
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list