Chapter 1-3

Hackers, Heroes of the Computer Revolution

There were two factions of TMRC.  Some members loved the idea of spending their time building and painting replicas of certain trains with historical and emotional value, or creating realistic scenery for the layout.  This was the knife-and-paintbrush contingent, and it subscribed to railroad magazines and booked the club for trips on aging train lines.  The other faction centered on the Signals and Power Subcommittee of the club, and it cared far more about what went on under the layout.  This was The System, which worked something like a collaboration between Rube Goldberg and Wernher von Braun, and it was constantly being improved, revamped, perfected, and sometimes "gronked"--in club jargon, screwed up.  S&P people were obsessed with the way The System worked, its increasing complexities, how any change you made would affect other parts, and how you could put those relationships between the parts to optimal use. 

Many of the parts for The System had been donated by the Western Electric College Gift Plan, directly from the phone company.  The club's faculty advisor was also in charge of the campus phone system, and had seen to it that sophisticated phone equipment was available for the model railroaders.  Using that equipment as a starting point, the Railroaders had devised a scheme which enabled several people to control trains at once, even if the trains were at different parts of the same track.  Using dials
appropriated from telephones, the TMRC "engineers" could specify which block of track they wanted control of, and run a train from there.  This was done by using several types of phone company relays, including crossbar executors and step switches which let you actually hear the power being transferred from one block to another by an other-worldly chunka-chunka-chunka sound. 

It was the S&P group who devised this fiendishly ingenious scheme, and it was the S&P group who harbored the kind of restless curiosity which led them to root around campus buildings in search of ways to get their hands on computers.  They were lifelong disciples of a Hands-On Imperative.  Head of S&P was an upperclassman named Bob Saunders, with ruddy, bulbous features, an infectious laugh, and a talent for switch gear.  As a child in Chicago, he had built a high-frequency transformer for a high school project; it was his six-foot-high version of a Tesla coil,
something devised by an engineer in the 1800s which was supposed to send out furious waves of electrical power.  Saunders said his coil project managed to blow out television reception for blocks around.  Another person who gravitated to S&P was Alan Kotok, a plump, chinless, thick-spectacled New Jerseyite in Samson's class.  Kotok's family could recall him, at age three, prying a plug out of a wall with a screwdriver and causing a hissing shower of sparks to erupt.  When he was six, he was building and wiring lamps.  In high school he had once gone on a tour of the Mobil Research Lab in nearby Haddonfield, and saw his first computer--the exhilaration of that experience helped him decide to enter MIT.  In his freshman year, he earned a reputation as one of TMRC's most capable S&P people. 

The S&P people were the ones who spent Saturdays going to Eli Heffron's junkyard in Somerville scrounging for parts, who would spend hours on their backs resting on little rolling chairs they called "bunkies" to get underneath tight spots in the switching system, who would work through the night making the wholly unauthorized connection between the TMRC phone and the East Campus.  Technology was their playground.  

The core members hung out at the club for hours; constantly improving The System, arguing about what could be done next, developing a jargon of their own that seemed incomprehensible to outsiders who might chance on these teen-aged fanatics, with their checked short-sleeve shirts, pencils in their pockets, chino pants, and, always, a bottle of Coca-Cola by their side.  (TMRC purchased its own Coke machine for the then forbidding sum of $165; at a tariff of five cents a bottle, the outlay was replaced in three months; to facilitate sales, Saunders built a change machine for Coke buyers that was still in use a decade later.) When a piece of equipment wasn't working, it was "losing"; when a piece of equipment was ruined, it was "munged" (Mash Until No Good); the two desks in the corner of the room were not called the office, but the "orifice"; one who insisted on studying for courses was a "tool"; garbage was called "cruft"; and a project undertaken or a product built not solely to fulfill some constructive goal, but with some wild pleasure taken in mere involvement, was called a "hack." 

This latter term may have been suggested by ancient MIT lingo-- the word "hack" had long been used to describe the elaborate college pranks that MIT students would regularly devise, such as covering the dome that overlooked the campus with reflecting foil.  But as the TMRC people used the word, there was serious respect implied.  While someone might call a clever connection between relays a "mere hack," it would be understood that, to qualify as a hack, the feat must be imbued with innovation, style, and technical virtuosity.  Even though one might self-deprecatingly say he was "hacking away at The System" (much as an axe-wielder hacks at logs), the artistry with which one hacked was recognized to be considerable. 

The most productive people working on Signals and Power called themselves "hackers" with great pride.  Within the confines of the clubroom in Building 20, and of the "Tool Room" (where some study and many techno bull sessions took place), they had unilaterally endowed themselves with the heroic attributes of Icelandic legend.  This is how Peter Samson saw himself and his friends in a Sandburg-esque poem in the club newsletter: 

Switch Thrower for the World,
Fuze Tester, Maker of Routes,
Player with the Railroads and the System's Advance Chopper;
Grungy, hairy, sprawling,
Machine of the Point-Function Line-o-lite:
They tell me you are wicked and I believe them; for I have seen  
            your painted light bulbs under the lucite luring
            the system coolies . . . 
Under the tower, dust all over the place, hacking with bifur-    
            cated springs . . . 
Hacking even as an ignorant freshman acts who has never lost
            occupancy and has dropped out
Hacking the M-Boards, for under its locks are the switches, and
            under its control the advance around the layout,
Hacking the grungy, hairy, sprawling hacks of youth; uncabled,
            frying diodes, proud to be Switch-thrower, Fuze- 
            tester, Maker of Routes, Player with Railroads,
            and Advance Chopper to the System. 

Whenever they could, Samson and the others would slip off to the EAM room with their plug boards, trying to use the machine to keep track of the switches underneath the layout.  Just as important, they were seeing what the electromechanical counter could do, taking it to its limit. 

That spring of 1959, a new course was offered at MIT.  It was the first course in programming a computer that freshmen could take.  The teacher was a distant man with a wild shock of hair and an equally unruly beard--John McCarthy.  A master mathematician, McCarthy was a classically absent-minded professor; stories abounded about his habit of suddenly answering a question hours, sometimes even days after it was first posed to him.  He would approach you in the hallway, and with no salutation would begin speaking in his robotically precise diction, as if the pause in conversation had been only a fraction of a second, and not a week.  Most likely, his belated response would be brilliant.

McCarthy was one of a very few people working in an entirely new form of scientific inquiry with computers.  The volatile and controversial nature of his field of study was obvious from the very arrogance of the name that McCarthy had bestowed upon it: Artificial Intelligence.  This man actually thought that computers could be SMART.  Even at such a science-intensive place as MIT, most people considered the thought ridiculous: they considered computers to be useful, if somewhat absurdly
expensive, tools for number-crunching huge calculations and for devising missile defense systems (as MIT's largest computer, the Whirlwind, had done for the early-warning SAGE system), but scoffed at the thought that computers themselves could actually be a scientific field of study, Computer Science did not officially exist at MIT in the late fifties, and McCarthy and his fellow computer specialists worked in the Electrical Engineering Department, which offered the course, No.  641, that Kotok,
Samson, and a few other TRMC members took that spring. 

McCarthy had started a mammoth program on the IBM 704--the Hulking Giant--that would give it the extraordinary ability to play chess.  To critics of the budding field of Artificial Intelligence, this was just one example of the boneheaded optimism of people like John McCarthy.  But McCarthy had a certain vision of what computers could do, and playing chess was
only the beginning. 

All fascinating stuff, but not the vision that was driving Kotok and Samson and the others.  They wanted to learn how to WORK the damn machines, and while this new programming language called LISP that McCarthy was talking about in 641 was interesting, it was not nearly as interesting as the act of programming, or that fantastic moment when you got your printout back from the Priesthood--word from the source itself!--and could then spend hours poring over the results of the program, what had gone wrong with it, how it could be improved.  The TMRC hackers were
devising ways to get into closer contact with the IBM 704, which soon was upgraded to a newer model called the 709.  By hanging out at the computation center in the wee hours of the morning, and by getting to know the Priesthood, and by bowing and scraping the requisite number of times, people like Kotok were eventually allowed to push a few buttons on the machine, and watch the lights as it worked. 

There were secrets to those IBM machines that had been painstakingly learned by some of the older people at MIT with access to the 704 and friends among the Priesthood.  Amazingly, a few of these programmers, grad students working with McCarthy, had even written a program that utilized one of the rows of tiny lights:  the lights would be lit in such an order that it looked like a little ball was being passed from right to left: if an operator hit a switch at just the right time, the motion of the lights could be reversed--Computer Ping-Pong!  This obviously was the kind of thing that you'd show off to impress your peers, who would then take a look at the actual program you had written and see how it was done. 

To top the program, someone else might try to do the same thing with fewer instructions--a worthy endeavor, since there was so little room in the small "memory" of the computers of those days that not many instructions could fit into them, John McCarthy had once noticed how his graduate students who loitered around the 704 would work over their computer programs to get the most out of the fewest instructions, and get the program compressed so that fewer cards would need to be fed to the machine.  Shaving off an instruction or two was almost an obsession with them.  McCarthy compared these students to ski bums.  They got the same kind of primal thrill from "maximizing code" as fanatic skiers got from swooshing frantically down a hill.  So the practice of taking a computer program and trying to cut off instructions without affecting the outcome came to be called "program bumming," and you would often hear people mumbling things like "Maybe I can bum a few instructions out and get the octal correction card loader down to three cards instead of four."

McCarthy in 1959 was turning his interest from chess to a new way of talking to the computer, the whole new "language" called LISP.  Alan Kotok and his friends were more than eager to take over the chess project.  Working on the batch-processed IBM, they embarked on the gargantuan project of teaching the 704, and later the 709, and even after that its replacement the 7090, how to play the game of kings.  Eventually Kotok's group became the largest users of computer time in the entire MIT computation center. 

Still, working with the IBM machine was frustrating.  There was nothing worse than the long wait between the time you handed in your cards and the time your results were handed back to you.  If you had misplaced as much as one letter in one instruction, the program would crash, and you would have to start the whole process over again.  It went hand in hand with the stifling proliferation of goddamn RULES that permeated the atmosphere of the computation center.  Most of the rules were designed to keep crazy young computer fans like Samson and Kotok and Saunders
physically distant from the machine itself.  The most rigid rule of all was that no one should be able to actually touch or tamper with the machine itself.  This, of course, was what those Signals and Power people were dying to do more than anything else in the world, and the restrictions drove them mad. 

One priest--a low-level sub-priest, really--on the late-night shift was particularly nasty in enforcing this rule, so Samson devised a suitable revenge.  While poking around at Eli's electronic junk shop one day, he chanced upon an electrical board precisely like the kind of board holding the clunky vacuum tubes which resided inside the IBM.  One night,  ometime before 4 A.M., this particular sub-priest stepped out for a minute; when he returned, Samson told him that the machine wasn't working, but they'd found the trouble--and held up the totally smashed module from the old 704 he'd gotten at Eli's. 

The sub-priest could hardly get the words out.  "W-where did you get that?" 

Samson, who had wide green eyes that could easily look maniacal, slowly pointed to an open place on the machine rack where, of course, no board had ever been, but the space still looked sadly bare.  The sub-priest gasped.  He made faces that indicated his bowels were about to give out.  He whimpered exhortations to the deity.  Visions, no doubt, of a million-dollar deduction from his paycheck began flashing before him.  Only after his supervisor, a high priest with some understanding of the mentality of these young wiseguys from the Model Railroad Club, came and explained the situation did he calm down. 

He was not the last administrator to feel the wrath of a hacker thwarted in the quest for access.