Rob Pike

Eventually, I decided that thinking was not getting me very far and it was time to try building.

— Rob Pike

Productivity is most important by engineering management rules, but enjoyment is most important for engineers. One stems from the other.

— Rob Pike

When there is no type hierarchy you don't have to manage the type hierarchy.

— Rob Pike

Not only is UNIX dead, it's starting to smell really bad.

— Rob Pike

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

— Rob Pike

Why would you have a language that is not theoretically exciting? Because it's very useful.

— Rob Pike

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

— Rob Pike

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

— Rob Pike

Narrowness of experience leads to narrowness of imagination

— Rob Pike

Rule 1. You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try…

— Rob Pike

A smart terminal is not a smartass terminal, but rather a terminal you can educate.

— Rob Pike

Caches aren't architecture, they're just optimization.

— Rob Pike

Languages that try to disallow idiocy become themselves idiotic.

— Rob Pike

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

— Rob Pike

There's no such thing as a simple cache bug.

— Rob Pike

There's nothing in computing that can't be broken by another level of indirection.

— Rob Pike

Object-oriented design is the roman numerals of computing.

— Rob Pike

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

— Rob Pike

Sockets are the X windows of IO interfaces.

— Rob Pike