The Supermen: The Story of Seymour Cray and the Technical Wizards Behind the Supercomputer / Edition 1

Hardcover (Print)
Buy New
Buy New from BN.com
$21.67
Used and New from Other Sellers
Used and New from Other Sellers
from $11.93
Usually ships in 1-2 business days
(Save 67%)
Other sellers (Hardcover)
  • All (14) from $11.93   
  • New (7) from $24.36   
  • Used (7) from $11.92   

Overview

The SUPERMEN

"After a rare speech at the National Center for Atmospheric Research in Boulder, Colorado, in 1976, programmers in the audience had suddenly fallen silent when Cray offered to answer questions. He stood there for several minutes, waiting for their queries, but none came. When he left, the head of NCAR's computing division chided the programmers. 'Why didn't someone raise a hand?' After a tense moment, one programmer replied, 'How do you talk to God?'" -from The SUPERMEN The Story of Seymour Cray and the Technical Wizards behind the Supercomputer

"They were building revolutionary, not evolutionary, machines. . . . They were blazing a trail-molding science into a product. . . . The freedom to create was extraordinary." -from The Supermen

In 1951, a soft-spoken, skinny young man fresh from the University of Minnesota took a job in an old glider factory in St. Paul. Computer technology would never be the same, for the glider factory was the home of Engineering Research Associates and the recent college grad was Seymour R. Cray. During his extraordinary career, Cray would be alternately hailed as "the Albert Einstein," "the Thomas Edison," and "the Evel Knievel" of supercomputing. At various times, he was all three-a master craftsman, inventor, and visionary whose disdain for the rigors of corporate life became legendary, and whose achievements remain unsurpassed.

The Supermen is award-winning writer Charles J. Murray's exhilarating account of how the brilliant-some would say eccentric-Cray and his gifted colleagues blazed the trail that led to the Information Age. This is a thrilling, real-life scientific adventure, deftly capturing the daring, seat-of-the-pants spirit of the early days of computer development, as well as an audacious, modern-day David and Goliath battle, in which a group of maverick engineers beat out IBM to become the runaway industry leaders.

Murray's briskly paced narrative begins during the final months of the Second World War, when men such as William Norris and Howard Engstrom began researching commercial applications for the code-breaking machines of wartime, and charts the rise of technological research in response to the Cold War. In those days computers were huge, cumbersome machines with names like Demon and Atlas. When Cray came on board, things quickly changed.

Drawing on in-depth interviews-including the last interview Cray completed before his untimely and tragic death-Murray provides rare insight into Cray's often controversial approach to his work. Cray could spend exhausting hours in single-minded pursuit of a particular goal, and Murray takes us behind the scenes to witness late-night brainstorming sessions and miraculous eleventh-hour fixes. Cray's casual, often hostile attitude toward management, although alienating to some, was more than a passionate need for independence; he simply thought differently than others. Seymour Cray saw farther and faster, and trusted his vision with an unassailable confidence. Yet he inspired great loyalty as well, making it possible for his own start-up company, Cray Research, to bring the 54,000-employee conglomerate of Control Data to its knees.

Ultimately, The Supermen is a story of genius, and how a unique set of circumstances-a small-team approach, corporate detachment, and a government-backed marketplace-enabled that genius to flourish. In an atmosphere of unparalleled freedom and creativity, Seymour Cray's vision and drive fueled a technological revolution from which America would emerge as the world's leader in supercomputing.

Read More Show Less

Editorial Reviews

Publishers Weekly - Publisher's Weekly
Before Bill Gates ever tinkered with an operating system, one name represented the cutting edge of computing technology: Seymour Cray. He pioneered the supercomputer and honed that edge through each model he engineered, including those built under the auspices of two companies he founded-Control Data Corporation and Cray Research. In this engrossing study, Murray, a senior editor at Design News magazine, follows the development and influence of the supercomputer from its origins as a WWII codebreaking machine through its Cold War application in developing nuclear weapons to its modern-day uses in weather research and other fields. Along the way, he shows clearly how the supercomputer brought us from the age of punchcards and vacuum tubes to that of transistors and, now, silicon chips. Drawing from extensive interviews, including the final one Cray gave before his death earlier this year from injuries sustained in a car crash, Murray also explores the personal side of the engineer, whose reputation as a brilliant, anti-corporate workaholic gave him legendary status in the computer industry. Murray's prose emphasizes information over liveliness, but his book, with its balanced mix of biography, history and technology, should interest more general readers as well as the digerati. (Feb.)
Library Journal
Though it strives to tell an exciting, fast-paced story of the development of the supercomputer-as Tracy Kidder's Soul of a New Machine (Avon, 1982) did so well with the minicomputer-this work falls flat, fast. Murray, a senior editor at an engineering magazine, recounts the story of the mad race, started in the midst of the Eisenhower years, to develop a supercomputer under the sui generis genius Seymour Cray. But the book is unfortunately larded with comments reflecting what is certainly the author's ulterior motive: to show how corporate management and bureaucracy inevitably muck up the best efforts of computer gods like Cray and his whiz-kid engineers. Murray's arguments are hardly convincing, and they detract from the main story. The writing is annoyingly gleeful and hagiographic; what engineers think up is "absolutely mind-numbing," and their computers are "awesomely fast." University libraries should take a pass; marginally recommended for other, flush, libraries.-Robert C. Ballou, Atlanta
Booknews
Tells the story of how Cray, described as the Evel Knievel of supercomputing, and his colleagues paved the way for the Information Age, drawing on interviews, including the last interview Cray gave before his death. Includes b&w photos. Annotation c. by Book News, Inc., Portland, Or.
Kirkus Reviews
The name Cray is to the computer world what Ferrari is to the automotive world: a synonym for sheer speed and engineering bravado. Here's the story of the man behind the name, from Murray, a senior editor at Design News.

Seymour Cray was among the young WW II vets who found an engineering job at Minnesota-based ERA, one of the companies that grew up in response to the continuing military demand for advanced computers. He was almost immediately recognized as a genius. Cray combined a quick grasp of theory with the willingness to sit and hard-wire his own circuits. It was his recognition, in 1954, that transistor technology allowed both greater speed and reliability that catapulted him into the front rank of industrial genius. Moving to the newly founded Control Data Company, at age 35 Cray produced the CDC 1604, the fastest machine ever built. Impatient with the corporate rituals of meetings, lunches, and political maneuvering, Cray soon moved CDC's research facilities to Chippewa Falls, Minn., and continued to design faster and faster machines. His design philosophy was unique: He insisted on building every new computer from the ground up, while resisting the temptation to base his designs on untried technology. Eventually his independence led him away from CDC to found Cray Research. The Cray 1, the first computer to adopt integrated-circuit technology, became the instant standard by which all other machines were judged. But by 1989, Cray's maverick ways led him to split from his own company, searching for even faster and better computers. By then, though, the loss of Cold War funding had changed the economic landscape; there were no longer customers willing to pay whatever it cost to get the fastest possible machine. The Cray 4, his last completed design, never reached the marketplace.

Murray tells the story of Cray compellingly, and few readers will be able to close the book without a regret at the passing of an age when such independent giants could rule the world.

Read More Show Less

Product Details

  • ISBN-13: 9780471048855
  • Publisher: Wiley, John & Sons, Incorporated
  • Publication date: 1/18/1997
  • Edition number: 1
  • Pages: 232
  • Sales rank: 891,624
  • Product dimensions: 6.22 (w) x 9.30 (h) x 0.87 (d)

Meet the Author

Charles J. Murray is a senior editor at Design News magazine. He has written on the computer industry and information technology for the Chicago Tribune and Popular Science, and he was the recipient of the 1994 Jesse H. Neal Editorial Achievement Award. Mr. Murray lives in Park Ridge, Illinois.

Read More Show Less

Read an Excerpt




Chapter One


The Codebreakers


For six days U-66 poked and prodded the gray water of the Atlantic Ocean, frantically searching for a place to surface, but the ships were always there. At any time of day or night the planes and ships would close in, and the crew of the U-boat would flee for their lives, hoping to find a safe haven.

    Now they were surfacing again. Kapitänleutnant Gerhard Seehausen, the U-boat's commander, would have preferred to come up at another time, in another place, but he was running out of options. Here in the mid Atlantic on the moonlit night of May 5, 1944, U-boat life was dangerous, but this was incredible. Everyplace U-66 went, it was hounded. It could barely surface without being stalked. Time was running out. Seehausen's U-boat could go no further without running its power generators, which provided electricity and light, and it needed to rendezvous with a refueling sub.

    With his U-boat at the water's surface off the Cape Verde Islands, Seehausen quickly sent a message to the radio room. The radio operator typed the message into a machine called Enigma, which scrambled its text; then he broadcast it to Berlin by tapping it out in Morse code: "Refueling impossible under constant stalking. Mid Atlantic worse than the Bay of Biscay." The message included the sub's location, a standard practice for all German U-boat transmissions. Seehausen never worried that Allied forces would intercept the message and crack the code during his hour at the water's surface. If they found him, as he knew they might, it would be by some meansother than cracking the code. Never by cracking the code. No one could crack the German Enigma code that quickly.


* * *


Minutes after U-66 surfaced somewhere near the African coast, a teletype clattered to life in a Washington, D.C., laboratory. The machine rattled away, sending the lab's operators into a frenzy. One grabbed the teletype's paper output and frantically keyed its message onto punched paper tape. Another fed the tape into a 7-foot-high, 5,000-pound calculating machine. Inside the machine, primitive logic circuits examined U-66's message. Outside, the lab's codebreakers anxiously awaited its response.

    Seehausen could never have imagined the scenario taking place halfway around the world. To think that someone was intercepting his message, then sending it across the Atlantic, where a 5,000-pound machine was stripping away its encryption codes would have been beyond the bounds of the most dedicated science fiction fans.

    For that matter the activity in the Washington, D.C., laboratory was beyond the imaginative scope of almost every U.S. government official. Other than President Roosevelt, few knew of the effort, mundanely titled Communications Supplementary Activity—Washington (CSAW). The decryption activity was cloaked by such secrecy that its highest ranking officials required Ultra Secret clearance—a security level even higher than that of the Manhattan Project.

    Roughly a thousand codebreakers worked at the navy's Nebraska Avenue facility—a tidy, red brick, former girl's school located in a quiet section of the city. These codebreakers were about as diverse and unconventional as any task force ever marshalled by the U.S. military. They had backgrounds in mathematics, physics, engineering, astronomy, and just about any discipline requiring intuitive pattern recognition. Some were chess experts, bridge champions, and musicians. Many had Ph.D's; a few were world-renowned scientists.

    When the war began, they had decrypted messages like those of U-66 without the benefit of machines. To do it, they had quietly labored over volumes of coded messages, searching for patterns that departed from pure randomness. When they had stumbled upon a pattern, they had conferred, discussed, debated, bickered, and fought among themselves until groups of them had finally arrived at a consensus. Sometimes it had taken as long as six hundred hours.

    As the war progressed, they developed machines to do the job. Following the lead of British scientists, a naval group in Dayton, Ohio, struggled to construct the machines, which they called Bombes. At first the Bombes were like 1930s adding machines, which used little electrical relays that clicked and clacked as their wheels spun furiously. By the end of 1943 the Bombes were far faster and more complex than electromechanical adding machines. By now they incorporated advanced circuits with more than fifteen hundred vacuum tubes.

    When technicians entered a coded message into its circuits, a Bombe could buzz through a decryption in about the same time as it took a thousand cryptanalytic clerks. It was uncanny. Somewhere in the Atlantic a Nazi technician would tap the keys of the Enigma machine and scramble a message in such a way that a codebreaker would have to try millions of permutations to crack it. And yet the machines could, in some cases, blaze through that code in a few minutes.

    Now the Bombes were cracking U-66's coded message—and it was about time. Since early in the war U-66 had done more than its share of damage. American intelligence blamed it for sinking the Allan Jackson, a 435-foot oil tanker owned by Standard Oil of New Jersey. They'd also blamed U-66 for sinking the Lady Hawkins, an ocean liner with 212 passengers on board, mostly civilians including women and children. Many sinkings were ugly: Victims swam through thick black smoke and layers of floating fuel, often burning to death alter the fuel was ignited by signal flares.

    But the tables were turning. The cryptologists at the Nebraska Avenue lab had cracked the code of U-66's message: "Refueling impossible under constant stalking. Mid Atlantic worse than the Bay of Biscay." Then came the most important information: "17 degrees, 17 minutes North; 32 degrees, 29 minutes West." Through a series of channels, the cryptologists relayed their information to the destroyer USS Buckley, which steamed through the mid Atlantic toward Seehausen's U-boat.

    Seehausen suspected that it was only a matter of time before Allied carriers and destroyers found him. They had been hounding him since April 29, and it was nearly midnight on May 5. Now he could see the USS Buckley about twenty-five hundred yards away. It was far too late to dive—an emergency dive could take as long as twenty minutes. He would have to face the Buckley, and he knew he had no chance of surviving.

    Seehausen would never know the truth about his sub's sinking. He would never hear about the red brick building or the cracking of the Enigma code. And he would never suspect that his sub's real nemesis was the ancestor of a machine that would one day be called the digital computer.


* * *


During the last of his four years at the navy's Nebraska Avenue facility, Lieutenant Commander William C. Norris started thinking about other uses for the codebreaking machines. Surely, he thought, there must be business applications for machines as fast as these.

    Bill Norris knew that the war would end soon and wondered about his options after he left the service. Unlike some of the other navy men, Norris had options. If he wanted, he could return to his family's farm in southern Nebraska, or he could go back to the Westinghouse Corporation in Chicago, where he had worked before the war selling X-ray equipment. A more staid personality might have done just that. After all, most of the country dreamed of little more than settling back into their prewar lives. But Norris wanted more, and he prided himself on his willingness to take risks to get it. A genuine, callous-palmed, Dust Bowl farm boy, he had traded his overalls for a slide rule thirteen years earlier, and at age thirty-five he wasn't anxious to go backward.

    At the red brick school Norris methodically worked his way up in rank, despite being surrounded by some of the country's best scientists. Unlike many of the other codebreakers, he didn't hail from a posh eastern college or have a distinguished track record of scientific achievement, but he was a quick study who was forceful and direct, almost to the point of bluntness. With his wide face and high cheekbones, he looked a little like the tough-talking character actor Sheldon Leonard. Though he was an average-sized man, he had an air of intimidation about him. When the occasion called for it, Norris could, as the saying went, curse like a sailor.

    Prior to joining the codebreakers, his crowning achievement had been in cattle farming. He'd grown up on a grassy spread of about a thousand acres along the Republican River in southern Nebraska. His life was classic midwestern Americana: small towns, rolling pasture lands, even a one-room schoolhouse.

    He had been a bright student, but because he'd attended a school with only seven or eight other children in the tiny town of Inavale, Nebraska, it was difficult to know just how bright. Life on the farm had made him practical, an improviser. He had a strong mechanical aptitude and a passion for radio technology. His bedroom was strewn with vacuum tubes and copper wire and he was a ham radio aficionado. Alter he finished high school, Norris went on to the University of Nebraska at Lincoln to study electrical engineering.

    Decades later, after Norris had achieved overwhelming success, the stories of his early years on his family's cattle farm would still be recognized as his defining moments. He returned home from the University of Nebraska in 1932, an electrical engineering degree in hand, and was hit with three crushing blows at once: His father had passed away a month earlier; the country was mired in the depths of the Great Depression; and the Midwest was wracked by the worst drought in the nation's history. The soil was so thin that it was being whisked away by the wind, and people in neighboring states were afraid to hang out laundry for fear it would be coated with brown dust while it dried.

    Cattle owners, too, were besieged by difficulties. Without crops, they had no feed for cattle. The corn on the Norris farm—which had always been used to feed the animals—was coming up in pathetic little stalks that rose about knee high and then wilted. Most of the other cattle farmers faced the same problems. Livestock buyers, recognizing the farmers' plight, were taking advantage of the situation by doling out painfully low prices for cattle.

    Norris refused to sell at distressed prices. The twenty-two-year-old college graduate consulted his mother and decided to feed the cattle Russian thistles. About eight inches long, soft, and green, the Russian thistles were young versions of tumbleweed—the kind that always seem to be blowing down the dusty street of some Western movie set. But Russian thistles weren't regarded as cattle food, and most farmers believed they would kill the cattle or, at the very least, lead to the birth of deformed calves.

    When Norris announced his plan to the neighbors, they as much as said he was crazy, but he ignored them. When they refused to help him stack the Russian thistle "crop" that covered his land, Norris hired vagrants at the nearby Red Cloud, Nebraska, railroad station to do it. And the cattle lived—for not one, but for two more winters—before he sold them at higher prices.

    Norris liked to repeat the story because he believed that it demonstrated his willingness to take risks. More than that, though, it showed that he was profoundly confident and had good instincts. What may have looked like big risks to others weren't risks at all in Norris's mind.

    Having been educated as an engineer, however, Norris wanted to try, his hand in the technical world. Alter two years on the farm, he interviewed for engineering jobs. Westinghouse offered him two positions: part-time engineer for $80 a month or full-time salesman for twice that much. Having survived the Great Depression, he opted for the logical choice and soon began working out of a Chicago sales office, traveling to accounts in various parts of Illinois, Iowa, and Nebraska, selling medical and industrial X-ray equipment.

    Despite success in sales, his heart was still in engineering. When the war broke out, Norris jumped at a chance to break into a hardcore technical position. He took a job as a civil servant with the Bureau of Ordnance, where he hunched over a drafting board in a bullpen with about a hundred other engineers who worked on fire control for antiaircraft guns. Eventually he signed on with the Naval Reserve, ending up at the red brick school in Washington, D.C.

    At the Nebraska Avenue analytical center Norris was in his element. Though he wasn't in an intellectual league with the scientific theoreticians, he was technically proficient, and his managerial style was well suited for the navy: smart, gruff, and practical. While working at the red brick school, he was promoted to lieutenant commander.

    At CSAW (pronounced "Seesaw" by the codebreakers) Norris made more technical contributions than at any other stage of his career. At one point he discovered a method for identifying the source of German radio messages: Transmissions from each individual U-boat, he said, had their own set of peculiar characteristics. If he was right—and if they could identify the U-boat that was sending the message—they would crack the codes far faster. Scientists, however, questioned Norris's unproven theories and balked at the risks involved in using them. The characteristics, they said, were peculiarities of the ionosphere—the weather—not the U-boat. When they questioned his idea, Norris simply bypassed them and put the technique into effect. If he was wrong, he said, they could call him on the carpet. He wasn't wrong.

    Three years later when Norris again pursued a risky course, he would change the face of technology. But at that time, the idea he pursued seemed downright absurd.


* * *


No one was sure who first raised the concept of commercial applications for the codebreaking machines. But Norris occasionally found himself sitting around one of the research labs at the Nebraska Avenue building, idly brainstorming with some of the other technical people. During those sessions, they often wondered aloud about other uses for their machines. In the beginning it had seemed like a joke. He and Commander Howard Engstrom, a former Yale University mathematics professor who headed the research operation, lobbed ideas at each other and at some of the other men in the lab. What about flight reservations? Air traffic control? Guided missiles? Flight simulators? The old Link Trainer, a flight simulator for military pilots, was stiff, slow, and unrealistic. Digital electronics, they reasoned, could make the Link Trainer smoother, faster, and more flexible.

    But all of them knew that the new technology needed more development. Sure, they could replace the electromechanical relays in the Link Trainers with digital circuitry, but the cost of the system would skyrocket. Same for air traffic control and flight reservations. Even though digital technology offered the potential for scorching speed, it wasn't yet economically viable.

    Still, their pipedream grew. It started to appear so real that they stopped thinking of it as a joke. One evening during their ramblings Engstrom mused about the looming end to the war, "I, for one, don't want to go back to Yale, so I'd like to think in terms of something else."

    Norris, Engstrom, and the others briefly considered continuing their work in a government lab after the war, but they were unanimous in their disapproval of that prospect. Next they discussed setting up a private company and working for the navy on a contract basis. A good idea, they all agreed, but it still wasn't enough. Cost-plus-fixed-fee government work was hardly a road to riches; in fact, it was barely a living. Someone proposed that they find companies to sponsor or invest in their start-up. Though their technology wasn't yet ready for industry, it could be with enough capital for development. Their game plan evolved, eventually calling for Norris, Engstrom, and the others to own half of the proposed company, while outside investors owned the other half.

    In an extraordinary display of entrepreneurial wisdom, high-ranking navy officials drummed up support for the idea. The navy's rationale was simple self-preservation. The war's end was looming and the Cold War was on the horizon. Cryptanalytic work would be as crucial as ever, even after the war, yet navy officials would be unable to order their codebreakers to remain at the Nebraska Avenue facility. Most of the codebreakers had already dismissed the idea of continuing their effort in civil service positions, so the navy had little choice: Either keep the existing group together or start again from scratch.

    Convincing the captains of industry to buy into their proposal, however, was another matter. In their own minds they could see how the technology might give a boost to, say, an airline company. A reservationist might talk to a business executive who wanted to fly from Chicago to Omaha. By punching a few keys, the reservationist could send the electrons zipping through bundles of spaghetti wiring, jumping across vacuum tubes, speeding through the logic circuits and electronic memory, where the information on the Chicago-Omaha flight would be stored as little magnetic bits of information. American Airlines at the time used "card boys," who dashed around the reservations office with little three-by-fives on which were scribbled the number of available seats for a flight. Given the state of the art, the need for electronic machines seemed obvious.

    Still, it was a hard sell. Norris and Engstrom polished their shoes and donned their aristocratic-looking white naval officer uniforms with their shiny gold buttons. Through their navy contacts, they managed to get audiences with presidents of companies such as American Airlines and Western Union. But their pitch—replete with references to electrons, logic circuits, and bits of magnetic information—sounded like voodoo to the baffled company executives. The executives sat politely and listened and their ears perked up every now and then at the thought of the potential corporate efficiency, but their answers were always the same.

    In the end it was simply too unrealistic. When it came to discussing reliability or past experience, Norris and Engstrom were handcuffed. They couldn't talk about past experience: All that information was classified and it was a felony to discuss it. They couldn't say how they'd used the machines, or for how long, or what their reliability record was. One of the few things they could say was that the machines existed.

    Worse, Norris or Engstrom could offer no business savvy. They were a mathematician and an engineer proposing an entry into a foreign domain, and the time simply wasn't right for taking on such a program. As the war drew to a close, most companies were reorganizing and rethinking their business plans. One after another the executives listened, then politely declined. It was a fine idea, an idea with great potential, they said. But the war had just ended, their company was reorganizing, funding was difficult to come by, the risk was too great.

    The navy, however, wouldn't let Norris and Engstrom quit. Determined to keep their cryptological programs afloat, naval officials arranged for the two to visit with James V. Forrestal, secretary of the navy and former Wall Street financier. Forrestal helped set up interviews with still more firms, including New York investment banker Kuhn Loeb & Co. But even there they met with resistance. Executives at Kuhn Loeb flatly concluded that there was no commercial future for their ... electronic calculators.


* * *


Norris had never heard of Northwestern Aeronautical Corporation. Northwestern, formed in conjunction with Twin Cities-based Northwest Airlines, made wooden gliders for the war effort. Allied forces used the unpowered gliders at the Normandy D-day invasion and at other battles to silently carry troops into enemy territory. The company assembled fifteen gliders a day in a huge plant on Minnehaha Avenue in St. Paul, Minnesota.

    Nor had Norris heard of John E. Parker, owner of Northwestern Aeronautical. Parker was a Naval Academy graduate, a social hobnobber, and an entrepreneur. A jovial, round-faced man with an amazing recall for names and faces, he was universally liked. Parker and his wife lived in Washington, D.C., about three months a year and spent the other nine months at the Commodore Hotel in St. Paul, a ritzy little hotel with a rich, dark wood decor and big, luxurious rooms. Despite his apparent wealth, John Parker was facing a potential financial crisis. As sole owner of Northwestern Aeronautical and part-owner of the Toro Company, much of his capital was tied up. Northwestern Aeronautical had a dim future, because with the war's end there would be no imaginable need for wooden gliders.

    For Parker, the disintegration of Northwestern Aeronautical would be a giant loss. He liked to claim that Northwestern was the second- or third-largest contractor to the war effort, and now his company was about to collapse with a suddenness that few businessmen ever experience. Parker was desperately searching for a solution to his problem when a high-ranking navy official called him. Through channels, the official said, he had heard that the navy was looking for an investor. He knew little about the opportunity because the information was classified. Highly classified. He told Parker to go back to Washington and to talk to naval officials there.

    Parker did, and was stunned to find that the first naval official they wanted him to meet was Admiral Chester W. Nimitz, former commander of the Pacific Fleet. It was clear that the navy was pulling out all the stops in its effort to find an investor. Parker was escorted into Nimitz's office, where the admiral shook his hand and jabbed a finger in his chest. "I've looked into your background and there's a job that I'd like you to do," Nimitz told him, "and it may be more important in peacetime than it is in wartime." Nimitz then made a fleeting reference to a particular naval group, saying that it was important to keep the group together. And that was it.

    Being an Academy graduate, Parker had the proper respect for naval authority. "Aye, aye, sir," he said, though he had no idea what he was agreeing to. Later Parker was ushered into the assistant secretary of the navy's office and then into the office of the judge advocate, who gave him legal advice on the matter. By the time Parker finally met with Norris and Engstrom, he was only aware that the navy thought that this proposed venture was vitally important. Or at least he was aware that the navy was trotting out its biggest names in an effort to woo him.

    Norris and Engstrom made the same pitch to Parker that they'd already made to a dozen other potential investors. They told him that they'd been involved in highly classified work and would like to continue it on a private basis, but that they needed an investor to pick up half the tab for their new venture. They promised at least three years of service and laid out a few of the potential business applications for the technology.

    After they finished, Parker still knew almost nothing about the proposed venture. Nimitz hadn't given him a shred of information about it, and had said only that it was of great importance to the country. Norris and Engstrom had provided a little bit more, but even their information was sketchy. They apologetically explained that it would be a felony to reveal any more, and Parker accepted their explanation. By the end of the fourth meeting they still hadn't told Parker who his new customers would be.

    Parker had grown wealthy as an entrepreneur and was far shrewder than any of the navy men suspected. No, he didn't understand digital electronics or vacuum tubes, and he couldn't assess the technical capabilities of Norris and Engstrom. But he could read between the lines. He implicitly understood that the company's main customer would be the navy—that was plain enough—and he knew that the navy had already assessed the capabilities of Norris and Engstrom. If Norris and Engstrom had come up short in its estimation, he wouldn't be here. It was a roundabout way of evaluating the situation, but it was all he had. Parker liked to tell his friends that it was a little bit like taking on a symphony orchestra without knowing a note of music, but that didn't worry him.

    Besides, there was this issue of Northwestern Aeronautical. Parker had already declared the glider factory as war surplus and had liquidated his inventory. The company was clearly on the verge of collapse—that is, unless he could pull off a last-minute miracle. And this new venture certainly fell into the category of a last-minute miracle. If he could pull it off, he knew that the new company could potentially offer jobs for his current employees. Whatever machines the navy men planned to make, machinists and assemblers would be needed to build them.

    Parker considered everything: the fate of Northwestern, the loss of jobs for all the machinists at his plant, the risk of investing in a project he didn't understand. But one image kept coming back to him—Nimitz jabbing a finger in his chest and saying, "There's a job I'd like you to do." In 1945 most of the country still felt a sense of common purpose and patriotism, and an order from someone the stature of Admiral Nimitz was almost impossible to resist, especially for a Naval Academy man. So Parker sold his $300,000 stake in the Toro Company to fund the new venture.

    Then he called together Norris, Engstrom, and Captain Ralph Meader from the Naval Computing Machine Laboratory in Dayton, Ohio. They and their wives met for dinner—in grand Parker style—at the Metropolitan Club in Washington, D.C. The navy men agreed to sign a contract binding themselves to three years of service to the new company; Parker agreed to head a group that would purchase a hundred thousand shares of the company stock at ten cents each. Pooling their resources, the navy men bought the other hundred thousand shares, and the deal was complete. Parker then returned to the St. Paul glider factory and announced to a band of cheering machinists that their jobs had been saved.

    In January 1946 the group incorporated the new company, calling it Engineering Research Associates (ERA). The navy men immediately hired forty members of the "Seesaw" staff, and Parker arranged for the new company to share his cavernous glider factory with Northwestern Aeronautical. Sharing quarters with Northwestern was critical because ERA wasn't yet qualified to carry out a major government contract. Although most members of its staff had worked for the navy during the war, ERA didn't have a corporate track record. Northwestern Aeronautical, however, did have a track record. So by setting up shop in the glider factory, ERA could work on major contracts that had been officially awarded to Northwestern Aeronautical.

    As far as the navy brass was concerned, Parker had saved their codebreaking operation. The machinists in St. Paul also considered Parker a savior—his last-minute heroics were responsible for saving their jobs. Norris and Engstrom were the only ones with an inkling of the business potential that could emerge from the new enterprise, but even they had more personal concerns. Parker's cash influx was helping free Engstrom from a life as a Yale math professor, and Norris no longer faced a return to his job as an X-ray machine salesman with Westinghouse.

    Everyone was pleased. They had taken an obscure military technology and transformed it into a private enterprise. They wanted to congratulate themselves for their foresight and steadfast determination, but Norris and Engstrom knew that their victory was not born of their own resolve. The real reason for the formation of Engineering Research Associates was that the U.S. Navy wanted it that way, and had pushed the company into existence through the bony finger of Admiral Chester W. Nimitz.

Read More Show Less

Table of Contents

The Codebreakers.
The Incubator.
Seymour.
Engineers' Paradise.
The Hog Trough.
The CRAY-1.
The Cray Way.
The New Genius.
Shakeout.
Notes.
Acknowledgments.
Index.
Read More Show Less

Customer Reviews

Average Rating 3.5
( 2 )
Rating Distribution

5 Star

(0)

4 Star

(1)

3 Star

(1)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 2 Customer Reviews
  • Anonymous

    Posted August 23, 2004

    a rather colorful, but sadly inaccurate, picture

    'The Supermen' was an luridly enjoyable (though quick) read... but there were sufficient inaccuracies that I doubt its overall veracity. There are far better computing histories available, although this book is one of the few to go into any detail about the early Control Data years. The book portrays Seymour Cray as some sort of computing 'god'. He was very definitely a smart guy, but I think it was more a case of 'in the right place at the right time' rather than any particular skill that made him the legend he is today. The biggest issue with the book is the lack of understanding on the part of the author. For example, he should've known that Cray did not invent the magnetic switch; An Wang (and Jay Forrester at around the same time) came up with the idea years before Cray suggested using it. Cray's idea of using out-of-spec transistors in logic circuits had been done before. He is attributed with many feats that are inherently impossible and/or absurd. Etc. I was able to identify many factual inaccuracies with the book without even trying. Cray was a self-promoter of the first magnitude, but a rather poor engineer. He had a few successes, in particular the CDC-160 and CDC-6600, but as time went on he was increasingly out of his depth. The success of Cray-1 was more a miracle (aided by many dedicated engineers) than any particular stroke of genius, and his subsequent designs ended up on the scrap heap of excess complexity. Nothing personal against Cray or the author, but this is a rather expensive book given the problems with it. For a far better look at the early years of computing, I'd suggest 'Building IBM' or 'Makin' Numbers: Howard Aiken and the Computer'. I'd love to see a factual and comprehensive book about the supercomputer era and its subsequent demise, but this isn't even close.

    1 out of 1 people found this review helpful.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted August 17, 2000

    The Rise and Fall of Midwest Computing Sans PLATO

    This is a great book, conveying much of the flavor of what it was like to be in the midwest's computing culture in its heyday of the 60's through the 70's. What it failed to do was tell the real story of the midwest's demise as computing leader of the world -- which isn't the story of Seymour's obsession with packaging over on-chip integration, as implied by this book. Rather it is the story of the failure to deploy the network revolution, now embodied in the Internet, to the mass market 20 years early on Seymour's matured hardware via the PLATO networking project at Control Data Corporation. PLATO was a $1 billion 'bet the company' investment by Bill Norris, the farmer/CEO of CDC who put a windmill pump from his Nebraska farm in front of CDC's corporate towers to remind people where they came from. That is the story of epic proportions only grazed on by this book. PLATO was ready to go to mass market, but Wall Street combined with classic middle mismanagement killed the mass market version of PLATO before it could even be test marketed -- for which it was ready. Had it gone otherwise, Seymour probably would never have left the midwest, and his supercomputer architecture would have focused more on the directions now being taken by Sun and Hewlett Packard -- except with Seymour's inimitable qualities. <p> I personally worked with the PLATO project and tested a version of it that would have leased a network computer with Macintosh-like interface, including network service, for a flat rate of $40/month with capital payback in 3 years. It had everything -- email, conferencing, user-programmable electronic commerce, multiuser realtime graphics games not to mention thousands of hours of computer based education courseware for which the PLATO system was originally designed. We could get this performance because the culture surrounding the land grant colleges of the midwest, such as the University of Illinois where PLATO originated, combined with Seymour's astounding performance levels created the right tradeoffs between hardware/software. Some of us were looking forward to incorporating Seymour's newly marketed Cray-1 as the foundation for the next generation of mass-market PLATO system -- and initial benchmarks looked to provide an outstanding bang for the buck as an information utility hub -- even without some of the more obvious architectural optimizations that would help in this new kind of application of his systems. This would have shielded Seymour from the vargaries of the government-dominated supercomputer market and driven his architectures into higher levels of silicon integration faster -- possibly providing the kind of capital in the kind of organization that could have delivered on gallium arsenide's potential, unlike the disaster that occured when Seymour left his farm and went cheek-to-cheek with the military in Colorado Springs, CO. <p> If you look at your Internet Explorer Help menu and select About Internet Explorer, you'll notice it is based on the NCSA Mosaic web browser and that it was developed at the University of Illinois -- right across the street from where PLATO was invented. This was no fluke. PLATO had a profound impact on the culture of the University of Illinois particularly its young students who wanted to push the envelope in networking. The NCSA also gave rise the most widely used web server, Apache, and the the founders of Netscape. The loss of possibly 20 years of 'new economy' is incalculable, but suffice to say, comparable losses have been suffered as the result of open war. <p> There are a lot of anecdotes this book doesn't tell that will probably die with the people who lived the tale. Just one, to capture a bit of what will be lost to history: <p> People looking for Cray Research's facility in the fields of Wisconsin could drive up to a farm house and ask where 'Cray Reserach' was located and friendly neighbor would say, 'Oh, you mean <i>Seymour's</i> place...' and then

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 2 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)