Procedure names should reflect what they do; function names should reflect what they return

Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is

Such is modern computing: everything simple is made too complicated because it's easy to fiddle with; everything complicated stays complicated because it's hard to fix.

Using Unix is the computing equivalent of listening only to music by David Cassidy.

Data dominates. If you've chosen the right data structures and organized things well, the algorithms will almost always be self-evident. Data structures, not algorithms, are central to programming.

Object-oriented design is the roman numerals of computing.

If POSIX threads are a good thing, perhaps I don't want to know what they're better than.