This is the second in a series of posts about Paul Graham’s book Hackers & Painters.
The second chapter of Hackers & Painters, the one that lends it title to the book, is easily condensed into a common aphorism: “Programming is more of an art than a science.”
The extended metaphor of the essay, how programs begin as sketches that morph and become filled in over time, is a bit overplayed. “In hacking, like painting, work comes in cycles. Sometimes you get excited about a new project and you want to work sixteen hours a day on it. Other times nothing seems interesting.” Well, isn’t that true of all endeavors? From studying economics to Quiz Bowl to building CarlWIki, I remember my entire undergraduate experience as an alternating series of bursts of interest. Even when I had a 9-to-5 job working at a college bookstore, there were days when I was excited about efficiently processing textbook returns (seriously!), and other days that were like watching grass grow.
There are also parts that ring hollow, perhaps simply because Graham and I are different kinds of hackers. He writes, “I like debugging: it’s the one time that hacking is as straightforward as people think it is. You have a totally constrained problem, and all you have to do is solve it. Your program is supposed to do x. Instead it does y. Where does it go wrong? You know you’re going to win in the end. It’s as relaxing as painting a wall.” Painting a wall is just one of many things I’d rather be doing than spending a whole day tracking down a bug. Walking slowly across a pit of hot coals is another. To me, the pleasure of hacking is the pleasure of turning a good design into a reality. I enjoy discovering unexpected subtleties—what I’d thought was a simple design might turn out to be quite intricate and delicate—but not outright bugs.
The highlights of the chapter to the people most likely to read Graham these days are the bits on business: “If you want to make money at some point, remember this, because this is one of the reasons startups win. Big companies want to decrease the standard deviation of design outcomes because they want to avoid disasters. But when you damp oscillations, you lose the high points as well as the low… So if you can figure out a way to get in a design war with a company big enough that its software is designed by product managers, they’ll never be able to keep up with you.”
Chapter 3 is a different kettle of fish. In “What You Can’t Say,” Graham starts by asking what heresies a time traveler from the future might be surprised by in our era. Then he broadens his scope: “I want to find general recipes for discovering what you can’t say, in any era.” This is not, of course, his true aim. As the chapter goes on, it gradually shifts away from being a how-to guide on identifying heresies toward being a combat manual for waging war on political correctness. It’s a deft tactical maneuver. Rather than standing up and shouting Larry Summers was right! (though he does mention him in passing), he merely suggests that smart people are more likely than others to “think unthinkable thoughts,” and advises that they be cautious in what they say.
As Graham allegorically explains: “Suppose in the future there is a movement to ban the color yellow. Proposals to paint anything yellow are denounced as ‘yellowist,’ as is anyone suspected of liking the color. People who like orange are tolerated but viewed with suspicion. Suppose you realize there is nothing wrong with yellow. If you go around saying so, you’ll be denounced as a yellowist too, and you’ll find yourself having a lot of arguments with anti-yellowists. If your aim in life is to rehabilitate the color yellow, that may be what you want. But if you’re mostly interested in other questions, being labeled as a yellowist will just be a distraction. Argue with idiots, and you become an idiot.”
At other times, he’s more explicit: “You can attack labels with meta-labels… The spread of the term ‘political correctness’ meant the beginning of the end of political correctness, because it enabled one to attack the phenomenon as a whole without being accused of any of the specific heresies it sought to suppress.” And: “What counts as pornography and violence? And what, exactly, is ‘hate speech’? That sounds like a phrase out of 1984.” And: “So when you see statements being attacked as x-ist or y-ic (substitute your current values of x and y), whether in 1630 or 2030, that’s a sure sign that something is wrong. When you hear such labels being used, ask why.”
Here Graham is advocating what countless smart people do but don’t talk about: Being iconoclasts internally without starting arguments wherever they go. They think outside of the box, but speak within it. “The problem is,” he sighs, “there are so many things you can’t say. If you said them all you’d have no time left for your real work. You’d have to turn into Noam Chomsky.” An awful fate for a hacker, indeed.

Or you can create your own world where you can say things… which works wonders until you have to interact with people outside of it.
The idea of attacking labels with meta-labels is interesting.
“That idea is fascist!“
“That critique is labelist.”