Rule of Silence: When a program has nothing surprising to say, it should say nothing.Someone needs to tell Microsoft that one so Windows XP can stop bugging me every 3 seconds about inactive desktop icons, or my computer being at risk, or new hardware being found, or....
CaptSnufy:Unix doesn't like long filenames either. However, many *NIX guis, including OS X, use them. In the command line, yopu have to either escape them by using the backslash or putting them in quotes.
I like this list, and the book, too...This list, plus good comments should be a mantra for all software...Repeat after me...:"Modularity""Clarity"...Thou shalt not reside in an ivory tower...Thou shalt comment...Thou shalt learn and grow and be open to new ideas...Thou shalt ignore "Not Invented Here(tm)" impulses...Thou shalt not have territories...
Good link, if only for the reminder about "The Art of Unix Programming." Great reading so far. ESR, while controversial, is still an interesting writer.-rcmiv
Definitely an interesting reminder. Most of these rules make sense, although some seem to conflict with agile development principles, which I find more important. In particular the Rule of Extensibility conflicts with YAGNI (You Ain't Gonna Need It). Keeping things simple and not thinking too soon about potential extensibility (which may or may not be needed) generally makes more sense to me, although it obviously depends on what you are building.
thankthecheeseDec 7, 2005
Rule of Silence: When a program has nothing surprising to say, it should say nothing.Someone needs to tell Microsoft that one so Windows XP can stop bugging me every 3 seconds about inactive desktop icons, or my computer being at risk, or new hardware being found, or....
caughtthinkingDec 7, 2005
there are better pages explaining this. this one goes into detail is a personal favorite of mine.<a class="user" href="http://www.faqs.org/docs/artu/ch01s06.html">http://www.faqs.org/docs/artu/ch01s06.html</a>this applies to *any* programming language or paradigm.i found it to be the truest, most consistent approach to programming i have ever found, so digg for that reason :)
flumpDec 7, 2005
Thanks for the replies, much appreciated.
paulypopexDec 7, 2005
@garagefighter ARF!
ickyelfDec 7, 2005
CaptSnufy:Unix doesn't like long filenames either. However, many *NIX guis, including OS X, use them. In the command line, yopu have to either escape them by using the backslash or putting them in quotes.
ursabearDec 7, 2005
I like this list, and the book, too...This list, plus good comments should be a mantra for all software...Repeat after me...:"Modularity""Clarity"...Thou shalt not reside in an ivory tower...Thou shalt comment...Thou shalt learn and grow and be open to new ideas...Thou shalt ignore "Not Invented Here(tm)" impulses...Thou shalt not have territories...
rcmivDec 7, 2005
Good link, if only for the reminder about "The Art of Unix Programming." Great reading so far. ESR, while controversial, is still an interesting writer.-rcmiv
digitalhobbitDec 8, 2005
Definitely an interesting reminder. Most of these rules make sense, although some seem to conflict with agile development principles, which I find more important. In particular the Rule of Extensibility conflicts with YAGNI (You Ain't Gonna Need It). Keeping things simple and not thinking too soon about potential extensibility (which may or may not be needed) generally makes more sense to me, although it obviously depends on what you are building.