James G. Sack (jim) wrote:
<heh> Maybe they're not all above everyone else. I only met one MIT CS grad, and he was a good programmer but had one particularly annoying desire to write one-big-thing, instead of modularizing.
Remember that how big a "thing" is depends on how smart you are and how much you can remember. The main good reason to modularize is to reduce complexity - if you can keep it all in your head at once, you don't have to modularize. Or pick good variable names. Or not reuse the same name to mean something completely different later.
(I've known a few people who are *way* too smart to write good code. The stuff works great, but it's utterly incomprehensible unless you can remember 1000 lines of code and what its doing.)
-- Darren New / San Diego, CA, USA (PST) -- KPLUG-LPSG@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
