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 — Rob Pike Copy Share Image
Eventually, I decided that thinking was not getting me very far and it was time to try building. — Rob Pike Copy Share Image
Productivity is most important by engineering management rules, but enjoyment is most important for engineers. One stems from the other. — Rob Pike Copy Share Image
When there is no type hierarchy you don't have to manage the type hierarchy. — Rob Pike Copy Share Image
Procedure names should reflect what they do; function names should reflect what they return — Rob Pike Copy Share Image
Why would you have a language that is not theoretically exciting? Because it's very useful. — Rob Pike Copy Share Image
If POSIX threads are a good thing, perhaps I don't want to know what they're better than. — Rob Pike Copy Share Image
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… — Rob Pike Copy Share Image
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… — Rob Pike Copy Share Image
A smart terminal is not a smartass terminal, but rather a terminal you can educate. — Rob Pike Copy Share Image
