Sure, now that is a fair request, here are some starting points:
* cat -v considered harmful: http://gaul.org/files/program_design_in_the_unix_environment.ps * The Unix Programming Environment: http://cm.bell-labs.com/cm/cs/upe/ * The Practice of Programming: http://cm.bell-labs.com/cm/cs/tpop/ * The various Software Tools series by Brian Kernighan * The Elements of Programming Style by Brian W. Kernighan and P. J. Plauger (ISBN 0-07-034207-5) * The Mythical Man-Month by Fred Brooks * The Elements of Style, aka Strunk & White (not computer related, but very relevant to good and clear style in programming and in design) * And of course the collection of Plan 9 papers: http://plan9.bell-labs.com/sys/doc/ There are a few more things, I should write them up some time, but this should make a good start. uriel On 1/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
On Fri, Jan 19, 2007 at 09:56:51PM +0100, Uriel wrote: > I say wmii is shit, because even if I will be ashamed of it all my > life(and good part of my afterlife), wmii is for the most part my > brainchild. And if you think wmii is great, then you got no fucking > clue about what decent software is. > > The sad thing is that compared with all the crap that floods the > (l)unix world this days, wmii is better than most other software, but > that only tells you how bad (l)unix has become. > > To end all this pointless noise I suggest to all the ignorant fools > that have no clue about software design, are ignorant of the unix > history, and could not tell sane software from a gnu turd even if > their life depended on it: to either start to get a clue and get over > the fact that all the software they use is shit, or to fuck off and > stop spamming. I'm a lurker here mostly, and wmii user, but I have a simple personal request. I hang out, and debate often with, a lot of academic computer-science types, as well as more practical-leaning software developer types. Usually, if I don't quite grok what they are saying off-hand, they can point me in the direction of an article, essay, book or two, that clears up confusion. So, are there 1 or 2 (or 9 or 10, even) articles, essays, softwares (besides the more obvious Plan9, ed, etceteras dicussed here) that you can suggest as a reference, that, when taken together, pretty much sum up together to be what you would like to seen in software? Thanks! I really am curious. __armando
