A moment ago he had told Hafner and Billo he didn’t know what he’d do next. If that had been true, it wasn’t any longer. He would create an incubator. This was the common term for an entity that helps entrepreneurs turn start-ups into actual companies, usually lending them advice and office space and sometimes money, in return for part ownership in the new enterprises. “There are lots of incubators. But I don’t care.” Seated in front of his computer but looking off toward nothing in particular, Paul went on, “If I did an incubator, here’s what the building would be like. It’s a four-story building in Boston. The fourth floor is for me and the Kayak guys. Let’s say it’s called Blade Boston. That would be the badass, elite, best engineering team in Boston. We do our own things but we also advise. You have to make formal application to become a member. If you make it in, you get: One, free real estate for a year. Two, I take ten percent of your company. Three, we help them with strategy, production, architecture, and financing, and once they get financing, we kick ’em out. It’s a four-story building. Floor one has a small kitchen, a small smoothie bar, a personal trainer room. Mind and body. It might be open to anyone in the tech Boston Blade community. There would be classes. The basement is a speakeasy, like from the 1920s. It would be public. And there would be an illegal private club on the roof, with a hot tub, pool, amazing sound system, and lights. I’d give it to my friends to use, with two requirements, that my bartender has to work it and my DJ…”
In his phone call, Paul had asked Billo and Schwenk if the three of them could meet for lunch the next day. Paul chose a place in Lexington, far enough from Kayak’s office in Concord that no one from work was apt to be there. He told his two lieutenants what he had in mind: an incubator that wouldn’t be called an incubator because most of those fail, but which would nurture start-up e-commerce companies that the three of them felt were promising. “Give them free room and advice and take ten percent of the equity, then get them financing and kick ’em out.”
“It would be a little holding company?” asked Schwenk.
“We put our own money in?” asked Billo.
“We have the choice,” said Paul. “We’ll shape them and improve them, then flip them to a VC. One of us then joins the board.” He added, “I’m thinking of calling it Blade, but I’m open to other names as well.”
It was a vague plan, almost a plan without a plan. But all three had the safety net of millions in the bank. They could withstand a failure.
“I could do it for a while,” said Schwenk.
“So could I, without hitting the college or retirement nest eggs,” said Billo. “I could totally do that.”
“Yup, I’m interested,” said Schwenk.
“Yeah,” said Billo. “It sounds very exciting.”
Schwenk looked thoughtful. “My only concern is not having enough to do. I don’t think I can code anymore.”
“Sure you can,” said Billo. “It’s riding a bike.”
Just like that, the matter seemed settled. Briefly, they worried aloud about the consequences for Kayak. Once the sale to Priceline was officially closed, Kayak would, as promised, remain an all but independent entity. Paul and Billo and Schwenk all agreed that they would have to arrange a transition in Concord’s leadership.
And then the tea and coffee came, and for a moment they reminisced, three old colleagues around a campfire. All three were still in their forties. They all looked in good shape but too old for starting companies—that is, according to the current legend, which had it that old age began when you started shaving.
“We started Kayak in our thirties,” said Billo. “We thought we were so old.”
“I was forty-one, I think,” said Paul.
Schwenk said, “I can’t imagine another nine-year project.”
“Neither can I,” said Paul. “But we could have flipped Kayak much sooner….” His voice trailed off.
Outside, in the pale, sunless winter air, on the gray suburban street, the world seemed drained of all color, but Paul was immune to dreariness just then. “That went well for me,” he said as he started his car, adding, “That was highly emotive for Billo.” Then he was musing out his windshield: “I’m going to sweep people in over the next few months with my enthusiasm. I could totally do it without Kayak people, but Billo and Schwenk and I have worked together a long time.”
He concluded, “Last night I resigned, and today I’m pitching something new. It’s an exciting time for me.”
Two days later, Paul wrote up a document, time-stamped at a little after four in the morning:
Blade incubator requirements
1. Space for 12 engineers (core team) expansion possibility for up to 30.
2. Maybe ~ 150 square feet per engineer (?)—thus spaces from 2,000 to 5,000 square feet?
3. Walk to MBTA.
4. A dozen restaurants and bars within a block or two.
5. Very hip feel. Distinctive from the street.
6. Very open space.
7. Move-in date June 2013 or sooner.
8. Lease or purchase options considered.
9. Parking options to be discussed.
PART III
A SMALL UNIVERSE
1
One is always aware that individual talent gets suppressed by societies, the gifted child mired in poverty. But there may also be a kind of talent that gets suppressed by time, a talent diffused within the human gene pool, which lies dormant awaiting its technological moment. One of the fathers of computer science, Donald E. Knuth, speculates that this was the case with computer programming. In a series of interviews published in Companion to the Papers of Donald Knuth, he is quoted as saying:
I’ve noticed that one out of every fifty people, more or less, has the peculiar way of thinking that makes them resonate with computers. Long ago, such people were scattered among many other disciplines, which didn’t quite suit their abilities, but they discovered each other when computer science was established as a separate field.
I mean, I think it’s likely that one out of every fifty people who built the pyramids, ages ago, would probably have been a great programmer if computers had existed in ancient Egypt.
In another conversation, Knuth refers to these born programmers as “geeks.” This used to be the name for carnival performers portraying wild men, but it had long since been reapplied to denote socially graceless eccentrics who might also be dedicated to a special field. More recently, it had also become a term of proud self-mockery. Knuth used it that way:
For simplicity, let me say that people like me are “geeks,” and that geeks comprise about 2% of the world’s population. I know of no explanation for the rapid rise of academic computer science departments—which went from zero to one at virtually every college and university between 1965 and 1975—except that they provided a long-needed home where geeks could work together. Similarly, I know of no good explanation for the failure of many unsuccessful software projects that I’ve witnessed over the years, except for the hypothesis that they were not entrusted to geeks.
In 2015, Knuth was a professor emeritus at Stanford. Oddly enough, way back in 1990, he had abandoned his public email address. There were several other ways of reaching him, which he had described on the Stanford University Computer Science website. You could use “good ol’ snail mail,” which he would deal with collectively, “in batch mode—like, one day every three months.” You could also fax him. “But be warned that I look at incoming fax mail last, perhaps only once every six months instead of three.” And you could try emailing him, via a couple of special impersonal addresses, but he would not answer any unsolicited emails, except for those that reported errors in his books.
All this suggested a most antisocial fellow, a Dickensian character who informs his public, “You can reach me by carrier pigeon, or, less reliably, by messages in bottles.” But one could sympathize. He was in his seventies now and trying to finish The Art of Computer Programming, a work of seven volumes. He had begun to write it in 19
62. In 2015, he was living on one of Stanford’s quiet residential streets, in a house that he and his wife had helped to design—he’d had a pipe organ installed in one of its rooms; he was a fine amateur musician. He spent long hours in his home office, creating drafts of Volume 4B of his gigantic book. That volume alone had grown, in concert with the rapidly expanding field it explored, to three lengthy volumes of its own, only one of which was finished. As he explained on the Stanford webpage, the work he faced was the kind that requires “long hours of studying and uninterruptible concentration.”
It wasn’t as if Knuth forswore communication with the world. He just wanted to do it on his own terms. Though he no longer taught regular classes at Stanford, he still gave half a dozen lectures a year. He played the pipe organ at his church (Lutheran), and, at least in the past, he had led a Bible study class. Over the years, his work had obliged him to confer with thousands of colleagues, and he welcomed readers who identified errors or made “significant suggestions.”
Knuth had received more than a hundred honors and awards, including the most prestigious available to computer scientists. These came mainly because of the first three volumes of The Art of Computer Programming. Those 2,200 pages had brought the rigor of analysis and mathematical proof to computer algorithms. More broadly, they had refined, assembled, and organized much of the best of what had been known and thought in computing, both the work of others and Knuth’s own discoveries. In the words of one admiring colleague, Knuth’s unfinished multivolume work had “established computer programming as computer science.”
The title of the book amounted to an assertion. In one of his essays, Knuth examines the meanings of “art” over time, and he concludes: “We have seen that computer programming is an art, because it applies accumulated knowledge to the world, because it requires skill and ingenuity, and especially because it produces objects of beauty.” He asserts: “Some programs are elegant, some are exquisite, some are sparkling. My claim is that it is possible to write grand programs, noble programs, truly magnificent ones!” In a book called Literate Programming, he sets out to show how programs can be explicated by their makers, not just to clarify their aims and methods but to turn them into works of art. “Programmers who subconsciously view themselves as artists will enjoy what they do and do it better,” he writes.
He had created many programs of his own. The largest and best known is called TEX (the name is derived from Greek and pronounced “tech”), a suite of software for computerized typesetting that includes a program for creating fonts. It was the first system that enabled computers to control the layout of text typographically and to print with the quality of hot-metal typesetting. Unlike many of the typesetting systems that followed, it adroitly handled mathematical and scientific notation. It was accounted a marvel when it first appeared, and more than thirty years later, both the original and variations of the system were still in use. Knuth never patented or licensed it; he had made the source code free and available to all.
His first publication was a spoof, “The Potrzebie System of Weights and Measures,” published in Mad magazine in 1957, when he was nineteen. He had been a prolific and versatile writer ever since. His Collected Papers alone now filled eight volumes. He had written books about mathematics and the Bible, also a collection of lectures and essays aimed at a general audience. In one of these, “God and Computer Science,” he writes: “I think it’s fair to say that many of today’s large computer programs rank among the most complex intellectual achievements of all time. They’re absolutely trivial by comparison with any of the works of God, but they’re still somehow closer to those works than anything else we know.” The point is unusual. Many have professed to see the hand of God in nature. But, as Knuth would have it, computer science is “an unnatural science,” a human invention that nonetheless opens a new lens on many theological questions. In the same lecture, Knuth suggests that programmers are positioned to catch “at least a glimmer of extra insight into the nature of God,” because programming often entails the creation of “a small universe.”
The nature of the art had changed in the span of Knuth’s career. Huge so-called libraries of software had accreted. Nowadays, many programmers worked without writing a great deal of original code, instead assembling code that others had written. But the world still needed some people to write what Knuth called “the innards of these magic black boxes.” Knuth said that his role in life was to serve this small cadre: “Somebody has to nurture them.”
These were his 2 percent. It had taken a machine to liberate their talents, indeed to liberate Knuth’s. He was not ungrateful. He considered The Art of Computer Programming the essence of his life’s work, and he had chosen to dedicate it not to a person, but as follows:
This series of books is affectionately dedicated to the Type 650 computer once installed at Case Institute of Technology, with whom I have spent many pleasant evenings.
2
In the English family’s house on Perham Street, the kitchen had contained seven boxes of cereal and flavors of ice cream, but there were no knickknacks on tables and few decorations on the walls. Paul’s father fixed everything himself. “That’s good enough,” he’d declare, and for the next several years there would be an unpainted patch on a wall or wires hanging from a ceiling. Paul’s mother, meanwhile, fashioned coffee filters out of paper towels, having calculated the relative expense.
One day in 1981, however, the summer after Paul’s junior year at Boston Latin, his mother came home with a brand-new thing, new from the store and still fairly new in the world—a personal computer, called a Commodore VIC-20. It cost $299.99, less than other personal computers but a fortune in his parents’ household. Paul couldn’t figure out just why his mother had spent the money. Maybe it was the scent of importance, spread by ads that claimed computers were great for helping kids with their homework. It might also have been the fact that Paul’s oldest brother, Ed, was now making a very good living programming computers.
The arrival of the VIC-20 felt like Christmas morning to Paul. Five years before, he had found it easy to turn away from the dumb terminals in the Latin School’s basement, but this was an actual computer. Just taking the VIC-20 out of the box—it looked like a typewriter with some additional and mysterious keys—felt like an utterly different experience. The little machine didn’t come with a display, but it was capable of producing images in color. Boston Gas had recently given Paul’s father a new color TV for his years of loyal service. When his father wasn’t home, Paul turned that TV, “the stupid box,” into the VIC-20’s screen. Hypothetically, the computer belonged to the entire household, but it was Paul who studied every one of the 164 pages of the VIC-20’s manual. The machine came with a few games, which he and his siblings played until they were experts. When the others lost interest, Paul took sole possession.
The little house had a half-aboveground windowless basement, built as a garage but long since turned into a single bedroom. A cellar stairway led down from the kitchen. The room felt like a separate place, especially at night when everyone was up on the top floor, two stories above. The converted garage had served as a haven for male adolescence, the burrow of several teenage boys in turn, first for Ed and then for the next oldest, Tim, who remembered the room as the place where he could turn up his Led Zeppelin records and smoke pot in peace. When Tim left home, Paul inherited the place. He had long since given up selling drugs and he only rarely smoked marijuana, but he often felt as if he were taking a drug when he retreated to that dark, dank room and lay on the single bed with his earphones on, the sweet, sad songs of Joan Armatrading drowning out the gurgling of the water heater beside him. He carried the VIC-20 down there. He bought a secondhand color TV to serve as its monitor and taught himself to write small programs—in BASIC, the computer’s built-in language. Later he would swear that the moment he saw computer code, he knew that he could write it. He could still get lost in lethargy down in his basement room, but much less often onc
e the VIC-20 arrived.
During Paul’s senior year at Latin, his brother Ed became a celebrity in the world of electronic games. Ed had left home and spent a year writing a chess-playing computer program for a company in Florida. It was a hit, and Parker Brothers had brought him back to New England and given him the task of converting a Japanese arcade game called Frogger into one that could be played at home on the Atari 2600 video game console. A difficult assignment, first of all because Atari didn’t want other companies producing games for its device, which meant that Ed, with the help of a colleague, had to reverse-engineer the Atari console to figure out exactly how it worked. More daunting, Ed had to reproduce Frogger in a program that would occupy only a smidgen of memory. He pulled it off in just six weeks. His version of Frogger was the first electronic game accompanied by two-part-harmony music. He called the experience “an Olympic trial for game-making” and the finished product “my Mona Lisa.”
Parker Brothers priced Ed’s version of the game at $20 per cassette and was already shipping four million copies to retailers when Ed brought a cassette over to Perham Street to show his masterpiece to the family. He set up the equipment on the kitchen table, and everything was going well until Paul started fiddling with the controls. The next thing Ed knew, the game went haywire. What’s more, Paul was able to make it malfunction again and again. Here was Ed’s baby brother, whom Ed had known only distantly and mainly from contentious games of chess—which Ed, to his chagrin, had usually lost—and now this teenage version of that irritating prodigy had found a bug in Ed’s Mona Lisa. Ed was furious—“I coulda killed him!”—and then he was scared. The code for the game was contained in ROM, read-only-memory chips, which could not be reprogrammed. For some time, Ed waited to hear that others had found the bug and were returning their cassettes, but no one ever did. Parker Brothers, having sold all four million of those cassettes in a year, offered to pay Ed $50,000 for every game he programmed thereafter. Instead, Ed quit and started his own gaming company, and soon afterward bought a brand-new Porsche and a house on the waterfront south of Boston.