Rob Pike's 5 Rules of Programming

This site does not allow itself to be embedded. You can still read it on the original site — the toolbar below keeps your place in the directory.

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. Measure. Don’t tune for speed until you’ve measured, and even then don’t unless one part of the code overwhelms the rest. Fancy algorithms are slow when n is small, and n is usually small. Fancy…

Read on koehr.ing ↗