To be a programmer is to develop a carefully managed relationship with error. There's no getting around it. You either make your accomodations with failure, or the work will become intolerable.

To be a programmer is to develop a carefully managed relationship with error. There's no getting around it. You either make your accomodations with failure, or the work will become intolerable.

I've always written. I'm from an older generation of programmers [who] did not come out of engineering. [A]ll sorts of people were drawn in from the social sciences and humanities.

We build our computer (systems) the way we build our cities: over time, without a plan, on top of ruins

The programmer, who needs clarity, who must talk all day to a machine that demands declarations, hunkers down into a low-grade annoyance. It is here that the stereotype of the programmer, sitting in a dim room, growling from behind Coke cans, has its origins. The disorder of the desk, the floor; the yellow Post-It notes everywhere; the whiteboards covered with scrawl: all this is the outward manifestation of the messiness of human thought. The messiness cannot go into the program; it piles up around the programmer.

The messiness cannot go into the program; it piles up around the programmer.

But you can't stop knowing something, can you?