Programmer time is expensive; conserve it in preference to machine time

Provided the development coordinator has a communications medium at least as good as the Internet and knows how to lead without coercion, many heads are inevitably better than one.

Often, the most striking and innovative solutions come from realizing that your concept of the problem was wrong.

In early 1993, a hostile observer might have had grounds for thinking that the Unix story was almost played out, and with it the fortunes of the hacker tribe.

And for any agents or proxy of the regime interested in asking me questions face to face, I've got some bullets slathered in pork fat to make you feel extra special welcome.

Given enough eyeballs, all bugs are shallow (e.g., given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone).

The only way to write complex software that won't fall on its face is to hold its global complexity down - to build it out of simple pieces connected by well-defined interfaces, so that most problems are local and you can have some hope of fixing or optimizing a part without breaking the whole