The Race For A New Game Machine:
By David Shippy and Mickie Phipps
()
About this ebook
The Xbox 360 and PlayStation 3 game systems have changed the face of home entertainment. But few know the amazing story inside the consoles—how David Shippy and his team of engineers at the Sony/Toshiba/IBM Design Center (STI) forged the tiny miracle at the core of it all: a revolutionary microprocessor chip that set a new paradigm in personal computing. At stake were the livelihoods—and sanity—of an unsung group of tireless visionaries. At war were the giants Microsoft and Sony.
"Drama and secret deals. . . This is the real deal." —Bob Molyneaux, ChipBridge
Here is a dazzling, behind-the-scenes account of life in the tech world, featuring memorable characters, high-level corporate intrigue, and cutthroat business dealings. It's a story that's never been told—until now.
"The real story of a team of people tasked with doing the impossible." —John C. Beck, author of Got Game
"Remarkable. . .fascinating." —Dean Takahashi, author of Opening the Xbox
"The story of the whole effort to build the Cell." —The Wall Street Journal
Related to The Race For A New Game Machine:
Related ebooks
Before the Crash: Early Video Game History Rating: 4 out of 5 stars4/5Swipe This!: The Guide to Great Touchscreen Game Design Rating: 4 out of 5 stars4/5Newb: A Guide to the Basics of Gaming Rating: 5 out of 5 stars5/5GameMaker Programming By Example Rating: 0 out of 5 stars0 ratingsBlood, Sweat, and Pixels: The Triumphant, Turbulent Stories Behind How Video Games Are Made Rating: 4 out of 5 stars4/5Game Work: Language, Power, and Computer Game Culture Rating: 5 out of 5 stars5/5Video Games: Design and Code Your Own Adventure Rating: 0 out of 5 stars0 ratingsHomebrew Game Development and The Extra Lives of Consoles Rating: 0 out of 5 stars0 ratingsBeginning Game AI with Unity: Programming Artificial Intelligence with C# Rating: 0 out of 5 stars0 ratingsGood Luck Have Fun: The Rise of eSports Rating: 0 out of 5 stars0 ratingsLibGDX Game Development By Example Rating: 0 out of 5 stars0 ratingsProcedural Content Generation for Unity Game Development Rating: 0 out of 5 stars0 ratingsVideo Game Careers - Beginners Guide: Video Game Careers, #1 Rating: 0 out of 5 stars0 ratingsWhat Happens When We Play: A Critical Approach to Games User Experience Design & Education Rating: 0 out of 5 stars0 ratingsNarrative Design for Writers: An Industry Guide to Writing for Video Games Rating: 4 out of 5 stars4/5Frictionless: Build Better Video Games, Attract and Retain Players, Grow Revenue Rating: 0 out of 5 stars0 ratingsA Comprehensive Guide to Video Game Design Schools Rating: 0 out of 5 stars0 ratingsThe Basics of Game Design Rating: 5 out of 5 stars5/5Mastering LibGDX Game Development Rating: 0 out of 5 stars0 ratingsMonoGame Mastery: Build a Multi-Platform 2D Game and Reusable Game Engine Rating: 0 out of 5 stars0 ratingsBuilding an RPG with Unreal Rating: 0 out of 5 stars0 ratingsGame Play™ Rating: 5 out of 5 stars5/5Developing Turn-Based Multiplayer Games: with GameMaker Studio 2 and NodeJS Rating: 0 out of 5 stars0 ratingsGlobal Game Jam Stories Rating: 0 out of 5 stars0 ratingsUnity Game Development Blueprints Rating: 0 out of 5 stars0 ratingsGame Logic: Level Up and Create Your Own Games with Science Activities for Kids Rating: 0 out of 5 stars0 ratingsPractical Game AI Programming Rating: 0 out of 5 stars0 ratingsCrowdgaming: The Role of Crowdsourcing in the Video Games Industry Rating: 0 out of 5 stars0 ratingsService Games: The Rise and Fall of SEGA Rating: 3 out of 5 stars3/5
Video Games For You
Live to Tell the Tale: Combat Tactics for Player Characters Rating: 4 out of 5 stars4/5The NES Encyclopedia: Every Game Released for the Nintendo Entertainment System Rating: 4 out of 5 stars4/5Dark Souls : Beyond the Grave - Volume 1: Demons Souls - Dark Souls - Dark Souls II Rating: 5 out of 5 stars5/5Pojo's Unofficial Advanced Pokemon Go: The Best Tips and Strategies for the World's Hottest Game! Rating: 5 out of 5 stars5/5The Monsters Know What They're Doing: Combat Tactics for Dungeon Masters Rating: 4 out of 5 stars4/5101 Awesome Builds: Minecraft® Secrets from the World's Greatest Crafters Rating: 4 out of 5 stars4/5Big Book of Zelda: The Unofficial Guide to Breath of the Wild and The Legend of Zelda Rating: 4 out of 5 stars4/5Fallout: A Tale of Mutation Rating: 5 out of 5 stars5/5Ultimate Guide to Mastering Command Blocks!: Minecraft Keys to Unlocking Secret Commands Rating: 5 out of 5 stars5/5The BIG Book of Animal Crossing: New Horizons: Everything you need to know to create your island paradise! Rating: 5 out of 5 stars5/5Pojo's Unofficial Ultimate Guide to Pokemon GO: How to Catch 'Em All! Rating: 3 out of 5 stars3/5Think Like A Game Designer Rating: 4 out of 5 stars4/5Pojo's Unofficial Big Book of Pokemon Rating: 3 out of 5 stars3/5The Super World of Mario: The Ultimate Unofficial Guide to Super Mario® Rating: 4 out of 5 stars4/5Legendary World of Zelda Rating: 4 out of 5 stars4/5The Ultimate Guide to The Legend of Zelda A Link to the Past Rating: 0 out of 5 stars0 ratingsQuest for the Golden Apple: An Unofficial Graphic Novel for Minecrafters Rating: 5 out of 5 stars5/5The Fortnite Guide to Staying Alive: Tips and Tricks for Every Kind of Player Rating: 5 out of 5 stars5/5The Gamer's Bucket List: The 50 Video Games to Play Before You Die Rating: 4 out of 5 stars4/5Master Builder Roblox: The Essential Guide Rating: 4 out of 5 stars4/5The Big Book of Five Nights at Freddy's: The Deluxe Unofficial Survival Guide Rating: 5 out of 5 stars5/5Phil Gordon's Little Gold Book: Advanced Lessons for Mastering Poker 2.0 Rating: 4 out of 5 stars4/5World of Warcraft: The Official Cookbook Rating: 5 out of 5 stars5/5The Sega Mega Drive & Genesis Encyclopedia: Every Game Released for Sega's 16-bit Console Rating: 5 out of 5 stars5/5Diablo: The Official Cookbook: Recipes and Tales from the Inns of Sanctuary Rating: 0 out of 5 stars0 ratings
Reviews for The Race For A New Game Machine:
0 ratings0 reviews
Book preview
The Race For A New Game Machine: - David Shippy
adventure.
PROLOGUE
THE EXCITEMENT BEGAN in the summer of 2003. My team and I had worked tirelessly at IBM for two and a half years, breathing life into the Sony PlayStation 3 Cell
central processing chip. My team was responsible for the PowerPC microprocessor core in the central processing chip. It was an important subcomponent in the overall chip that performed the function of the brains
for the entire PlayStation 3 game console. Our microprocessor core executed the instructions of the game console operating system and controlled the flow of information just like a traffic cop in a busy intersection. We ordered our lives around the idea of beating Microsoft to market with a Christmas 2005 launch of a revolutionary new game machine certain to soar to new heights of computing power and market share. Gamers worldwide would flock to this platform to blow away ghouls, race speedboats, and seduce bikini-clad vampiresses. With Sony’s dream to extend its empire to take over the home-computing business, a second and almost as consuming focus was the race with Intel and Advanced Micro Devices (AMD) to develop the chip that would surpass the world’s current performance record.
Then Dr. Chekib Akrout, IBM’s senior vice president responsible for the PlayStation’s chip team, told me another customer wanted our secret-weapon, record-smashing PowerPC microprocessor core. It was Microsoft.
We sat alone in his office, a barren, windowless hole on the sixth floor of an IBM building in Austin, Texas. Akrout leaned forward in his big leather executive chair and watched me, tapping his pen on his desk, waiting for my reaction to this shocking news. I was confused. Sony had agreed that IBM could use the PlayStation 3 PowerPC microprocessor core in other applications in the future, so IBM was on solid legal ground. Nevertheless, this new deal raised some sticky ethical questions in my mind. Wouldn’t we be competing against ourselves? Two-timing? Sleeping with the enemy? Sony was my partner! My temples pounded. Fury gripped my throat.
I was so angry I didn’t dare look at Akrout, so I swiveled my chair to the side and glared at the drab, bare wall instead. I wanted to make a competitive difference for Sony, who commissioned this little work of art. I spent years building a chip for them that would power their game machine to crushing victory in the marketplace, and it was a dream I was not ready to relinquish. While I fully expected our breakthrough chip to continue into future products in some derivative form, I never imagined it would happen before the current job for Sony was finished. I wasn’t ready to consider the demands of an additional customer, especially one that presented such a vast conflict of interest.
How did this happen?
I grumbled through gritted teeth, still looking at the cracks in the yellowed wall. Fluorescent lights buzzed and flickered above me, creating weird shadows that bumped into each other in the corners of the room.
Let’s just say it was a blockbuster, an offer IBM couldn’t refuse,
he answered. Lest I think the stakes of the enterprise were small, Akrout told me that over a billion dollars was involved, spanning the entire spectrum from development to chip manufacturing. Microsoft’s Bill Gates approached Sam Palmisano, IBM’s CEO, about designing the next generation Xbox microprocessor chip. The IBM sales team laid out every other chip option they possessed or could dream up, but nothing caught the interest of Gates’s team. Then a senior IBM engineer from another division disclosed to Microsoft some of the most sensitive details of the microprocessor core I was designing for the Sony chip.
My jaw dropped at this news, and I spun around to face Akrout. That was my baby! It was as if they had snuck an unauthorized Polaroid out of the labor and delivery room and posted it on the Internet. This was personal. IBM is a big company, spread across many locations and organized into a complicated web of semi-related divisions, each with its own mission, its own independent team. Even so, I had a reasonable expectation to be included in any discussions with potential clients for my processor. I fumed and raged about the subterfuge, but in the undercurrents beneath my anger, a more familiar beast took a deep, satisfying breath—my pride. Microsoft’s interest was flattering, a high compliment to my team’s virtuosity. We designed the fastest microprocessor in the industry, one that broke numerous performance records. It was tiny, and it consumed very little power. We gave Sony’s little game box the performance of a supercomputer, driving a deep shaft into a goldmine of riches for IBM that would endure for years.
Dave, you and your team have done an amazing job. I’m proud of your work.
Akrout was quick and generous with his praise, and because of my respect for him, his approval meant a great deal. Grinning, he added, It was your team’s microprocessor that turned Microsoft’s head and convinced them to strike a deal with us.
Of course it did,
I retorted, rocking forward in my chair. That’s the only thing he’d said that hadn’t surprised me. Given all the bad blood between IBM and Microsoft, I’ll bet they considered every other option before they came to us, didn’t they? And I can tell you what they discovered. The folks at Intel and AMD can’t deliver anything like this.
Did I mention that we chip designers are as competitive as Top Gun pilots?
There’s more,
Akrout said. He sank back into his chair, a subtle shift of body language, but enough to tell me he didn’t like relaying the next tidbit of news any more than he had the first. He ran a hand across his thinning black hair and sighed. Microsoft wants something very similar to what you designed for Sony but with some unique enhancements, and they want it on the same schedule.
He then described the design changes Microsoft needed for a super-aggressive, market-shaking Christmas 2005 launch.
That’s crazy!
I shouted, and slapped a hand down on the table. It’s practically a total redesign. It took us two and a half years to get to this point on the PlayStation 3, so how does Microsoft think they’re going to hit the same schedule? I mean, even if we could do our part and deliver a chip to them on time…and I’m extremely doubtful we could…how can they possibly do all the stuff they have to do to get a console ready by then and also have games available to play on it?
Akrout didn’t blink. It took me a second, but I got the message. He was such an optimist, he actually thought Gates’s people might just pull it off, with our help.
I slumped into my chair again, waiting for the next shoe to drop, while Akrout morphed into a used-car salesman—his sly grin, a smooth-as-silk voice, that sophisticated French accent. In addition to your role on the PlayStation 3 chip, I want you to take the technical lead position for the Microsoft microprocessor project,
he said. You’re the only person with the knowledge and skills to pull it off on this insanely aggressive schedule.
I had extremely mixed feelings about the offer. I was flattered but still felt like a two-timer. I loved Akrout. In his finest moments, he was completely capable of convincing his people to follow him over a cliff. He knew exactly where my buttons were, knew I couldn’t resist a high-flying challenge. I was such a sucker. My plate was already full, as was that of my team. I rarely got home in time to tuck my little boys into bed at night. Piling on more work, especially work that approached the shady side of impossible, would not be smart.
After some internal debate, my pride delivered a deathblow to my anger and perhaps to my common sense. I’m pretty sure one of us is going to regret this,
I said as I shook Akrout’s extended hand. I accept your offer.
My goals were very clear when I joined IBM in the mid-1980s. I wanted cutting-edge microprocessor design projects that really pushed the state of the art. I wanted to lead design teams and leave my mark on the industry. This vision was the focal point of my whole career. Akrout handed me one of the top technology leadership positions in the entire industry and, for one brief moment, I saw the top of the mountain, everything I wanted. Would I have to stake my claim by screwing Sony and extending Microsoft’s dominance of digital life? Or could I help them both succeed?
CHAPTER 1
The Holy Grail Vision
At the heart of every successful technical accomplishment, there first existed a bold vision that inspired the team.
Onward Through the Fog. Live Music Capital of the World. Hillary Is Hot! You’re just jealous because the voices only talk to me. Save the Giant Flying Vampire Armadillos.
THIS STRANGE ARRAY OF BUMPER STICKERS on the Volkswagen van in front of me held my attention a moment too long, and I almost missed my turn. I take pride in being a nonconformist, but in Austin, Texas, where Keep Austin Weird
is the city slogan, I clearly reside deep in normal
territory. It was February of 2001, and little did I know that I was about to jump on board the ride of my life.
I parked in front of the Gingerman Bar, the epitome of Austin’s funky hippie-yuppie lifestyle. It was once a favorite hangout of mine, and I hadn’t been there in years. I came to meet an old friend who wanted to discuss a job with me. A secret interview, he’d cautioned seriously when he phoned. I came mostly out of curiosity, for I was not in the job market. I glanced around the parking lot but didn’t see anyone I knew, no one to break my cover—I already disliked all this cloak and dagger stuff.
A cool breeze cut through me when I stepped out of my car, making me glad I’d swapped my baggy cargo shorts for a pair of faded jeans. Sandals flapped against my heels as I walked. No suit, tie, and spit-shined shoes, no well-crafted resume in hand. I heaved open the massive door, pulling against the wind. I barely squeezed inside before the door sucked closed behind me with a bang, nearly hitting me in the heels. I glanced into the entryway mirror and brushed a hand across my hair, but it was stubborn and chose to stick straight up despite my best efforts. Good enough, I thought, as I flapped a hand at my disheveled reflection.
Dim overhead lights and meager sunlight from the grimy windows did little to brighten the spacious bar. I snagged my Oakley sunglasses into the top buttonhole of my Hawaiian shirt.
Shippy!
I turned and moved in the general direction of the voice. Even though I couldn’t see well enough to identify the speaker, I knew who it was: the man I came to see. My eyes adjusted, and I spotted Jim Kahle in a corner booth. I lifted a hand in recognition and headed that way, weaving between a jumble of mismatched tables and chairs where a handful of patrons sipped tall glasses of beer.
I studied my old friend as I approached. He was fortyish, but he looked as lean and athletic as ever. Yellow polo shirt tucked into faded blue jeans. Well-worn running shoes. He still brushed his wavy sandy-blond hair straight back, but now it revealed a deeply receding hairline and a sunburned forehead.
He stood up to greet me, and we shook hands and patted each other on the back. Two years had passed since the last time we met, so all week I’d looked forward to seeing him again.
Kahle and I shared a long intertwined history as microprocessor designers at IBM. We first met in the fall of 1989 when I transferred from Endicott, New York, to Austin, where Kahle became my manager. We clicked right away. We both possessed an aggressive style, a hard work ethic, and a victory or death
attitude about work and life in general. We found common interests outside of the office including soccer, water skiing, and drinking beer. Ten years later, at the height of the technology boom, I left IBM to seek my own mythical dot-com fame and fortune at a local startup company. Kahle stayed on at IBM, diligently climbing the corporate ladder, becoming a Distinguished Engineer, a recognized force throughout the company. His team produced the microprocessor chips that put IBM in the lead in high-performance Unix servers and powered Apple’s resurgence in the personal computer market.
I slipped into the opposite side of the booth, sinking into well-worn burgundy leather. I teased him about the need for secrecy. What’s up with that?
I asked. Don’t tell me…the CIA wants us to solve the problems with global security, right?
Kahle just smiled, looking every bit like the cat that swallowed the canary. We’ll get to that,
he said. He had a secret worth sharing, but he was going to play it for all it was worth. He bought the beer, so I didn’t mind waiting.
We talked about our families, caught up on personal events of the past few years, sipped on frosty mugs of dark beer. Kahle’s three children were a couple of years older than my two sons, but still close enough in age that we had a lot in common. Parenting can be the universal leveler.
A half-hour passed, and I glanced at my watch. When would Kahle get to the heart of the matter? Silence settled heavily into a momentary gap in our conversation, and the polite pleasantries ended abruptly.
Kahle leaned across the table, whispering inspired words charged with intensity, filled with passion. He described a powerful partnership recently formed between Sony, Toshiba, and IBM to build the processor for the next version of the PlayStation game console. Sony was the biggest game player in town, with over 55 million PlayStation and PlayStation 2 units sold worldwide. Game developers flooded the shelves with over 430 million copies of game software for the PlayStation line. There were no official announcements of the partnership yet, and Sony insisted on keeping it quiet for as long as possible. Hence the need for secrecy.
With this project,
Kahle said, we have the potential to hit a home run and take over the entire home computing market. Or
—he paused and shrugged his shoulders—we could just hit a single and go build a cool chip for a game machine the whole world loves. At the very worst, we’d have some fun.
Both prospects intrigued me.
I took a long pull from my beer. These babies weren’t just toys—they were high-performance computing engines. Music to my ears. I’d worked on microprocessors for everything from mainframes all the way down to notebook computers. Designing a game machine would be a welcome change, and the software would be much sexier than the corporate stuff running on most of my previous designs.
Okay. You’ve got my attention,
I said.
Kahle squirmed and continued with his story, setting the bait. He represented IBM when these three high-tech giants collaborated on an idea for the PlayStation 3, a revolutionary game machine intended to turn the electronic games industry upside down. I was shocked at the extraordinary amount of money involved in this endeavor. Sony, Toshiba, and IBM agreed to spend $400 million over five years to develop the processor for this machine. Kahle’s eyes gleamed as he told me that this path-breaking, joint development venture, dubbed the STI Design Center, would be located right here in Austin. On top of that, this powerful threesome planned to spend billions of dollars for two state-of-the-art chip fabrication facilities. Sony also agreed to pay IBM hundreds of millions to set up a production line at their new facility in Fishkill, New York. That’s a lot of money to spend before a single chip rolls off the line.
Sony’s Ken Kutaragi was the instigator who brought the three companies together for this adventure,
Kahle said with just a hint of triumph in his voice. He looked disappointed when I failed to respond with appropriate awe. Kutaragi is president and CEO of SCEI, Sony’s video games division.
Oh.
I wiped off some of the gathering condensation on my mug, stalling for a moment while I considered this. I’ve been a little busy the last few years.
But he’s known everywhere as the father of the PlayStation.
Jim emphasized his words with extended arms, palms up. He studied my face, apparently looking for some aha moment, some sign that I recognized this famous man.
Jim, I barely know what a PlayStation is.
Hmph,
he said, shaking his head, still unable to fathom the depths of my ignorance. Okay. So I’ll give you a quick education. Kutaragi single-handedly led Sony into the game world, and the PlayStation game machines and software became the heart and soul of Sony’s business model. It’s their most successful product ever. With the PlayStation 1 and PlayStation 2’s phenomenal success in his pocket, Kutaragi felt he must and could realize a grander dream for the broadband market looming on the horizon. He wanted the PlayStation 3 to be a personal computer that also played games, with a chip that could take on roles in many broadband applications, from on-demand television to online gaming to real-time video chats.
As J. R. R. Tolkien might have put it, I thought, One chip to rule them all / One chip to find them / One chip to bring them all / And in the darkness bind them.
Remarkable,
I said, struck more by Kahle’s admiration for this man than by the story itself. Kahle is not one who is easily impressed.
Kahle was on a roll and went on to describe Kutaragi’s reputation as an excellent problem solver and a forward-thinking engineer. That proved true enough during the project planning stages, though I also found him to be demanding and unyielding. To achieve his vision, Kutaragi needed help from experts in processor development and silicon manufacturing. Sony brought expertise in consumer markets, Toshiba in high-volume products and we, IBM, brought microprocessor and system design experience.
That’s a pretty high-powered partnership for just one chip-development effort,
I mused.
Oh, it may be just one chip, but it’s much more than just one product,
Kahle replied. The building-block potential of this processor inspired each company to nurture visions of using this design in their traditional product lines. Toshiba plans to incorporate it in high-end televisions, and IBM is contemplating using the new chips in high-performance servers.
Maybe I didn’t know Kutaragi, but I still recognized the rare opportunity this partnership represented. When Kahle took a breath, I reached across the table and shook his hand, congratulating him on his accomplishment. It’s a well-deserved honor for you to serve as IBM’s point man for negotiations with Sony. Outstanding!
Kahle modestly claimed he was just lucky, but I knew differently. He was bright, maybe even brilliant. After graduating from Houston’s Rice University, he accepted an assignment with IBM’s research group, the beginning of a career-long tie to the folks in Yorktown, New York. His first assignment took him into design tools—money-saving, software-based programs that improved the quality of a design by automatically checking for errors, cross talk in the wires, and other design points that exceeded acceptable limits. He integrated those cutting-edge tools into the design process for the chip that eventually put IBM in the lead in high-performance Unix servers.
Kahle spent nearly twenty years of his life at IBM, serving as a key player on several highly successful development efforts including the breakthrough server chip known as the Power4 Gigaprocessor. He was very smart and very aggressive, big reasons why he was one of the most influential engineers at IBM.
I recalled the first time he invited me to play soccer. I scrounged around in my closet, found my old cleats, and brushed off the dust from a few years of neglect. Half an hour on the field and I was stiff, sore, and exhausted, but not giving up. I joined Kahle on the front line, and we tag-teamed the ball toward the goal. When we failed to score, Kahle ran across the field and screamed in my face for not hustling enough. He prided himself for being the fastest, most aggressive player on the field. He made up for any lack of ball-control skills by out-hustling his opponents. He was a bully, but I admired his competitiveness.
Whether playing soccer or designing a new chip, losing was not an option. Kahle was quick to reject those who didn’t agree with him, and more than one IBMer’s career suffered for crossing him. The Sony chip lay on Kahle’s career path; it was his next stepping stone. Nothing would keep him from success. I was more than a little flattered that he saw me as an asset in that venture, but I remained on the fence about joining up. I enjoyed the impact I could have in a small company. Going back to a big company like IBM wasn’t exactly appealing.
I drained my mug and then motioned to our waitress for another round.
Kahle described his new design center, which fell under the auspices of IBM’s Microelectronics Division. I spent the first few months of the STI partnership serving as the director in charge of both business and technical issues, even helping to write the contract. Boring stuff. As you can imagine, I was dying to get involved in chip design. The technical complexity of the chip soon consumed my interest, my energy, and my time, leaving little for the business side of things. Paperwork fell into complete disarray, I had no time for staffing, and the executives started to worry.
I doubt anyone could handle both of those challenging jobs,
I sympathized. As I well knew, Kahle was a technical wizard. He would perform much better in an engineering position than he would in a management or business role.
"Maybe not, but I quickly found out that I didn’t want to handle both jobs. I took the title of chief engineer, focusing on what I do best, chip architecture. I let others handle the contracts, financial controls, staffing, and other adminis-trivia. Finally, I was in the right place."
I had no doubt he’d made the right decision. He wielded a strong influence over any IBM team, and they generally accepted his technical command as absolute rule.
Kahle finally zeroed in on the point of our meeting. One of the first jobs he needed to fill was that of the chief architect for the PowerPC microprocessor core, the brains
of the chip. That’s where I need you, Shippy. You’ve always delivered high-quality innovative solutions for me.
I liked the sound of that. As the chief architect, I would take on the coveted role of the technical lead, defining the fundamental blueprint for the PowerPC microprocessor core. It was a once in a lifetime opportunity, the kind of job every engineer desires. It would allow me to exercise all of my creative and innovative engineering muscles and have a major influence on the design. I leaned back in the booth, ignoring the creaking of the old leather seat, and looked Kahle in the eye. Cutting-edge technology, a chance to be in the thick of things, a key leadership position, ground-floor opportunities—who wouldn’t be interested?
Kahle sensed a win and immediately moved to close the deal. This project is extremely important to the IBM Corporation, and folks like you, hired into key positions, will be heavily rewarded.
I smiled at that. He definitely knew the way to my heart. I said, You just caught yourself a fish.
We spent another hour or so reminiscing about the good times we’d enjoyed together in the mid-1990s at the Austin-based Somerset Design Center, a joint venture between IBM, Motorola, and Apple. Somerset challenged Intel for the PC market with a sleeker, cleaner, PC version of IBM’s standard Power server chip, called PowerPC. The Somerset office lay outside the main IBM campus, purposefully free of most of the bureaucracy found in industrial giants, thus creating the impression of a small, privately-run company. It was IBM’s bid to give its entrepreneurs the freedom to create and to invent. Kahle’s team delivered the first Somerset microprocessor, the PowerPC 603, and then Kahle brought me on board to architect the follow-on microprocessor, the PowerPC G3. Exciting times! The engineers on my team actually believed they could beat Intel, and I guess I did, too. We worked long and hard on our chip designs, and we frequently ended the day on a sand volleyball court at the design center or at the nearby Arboretum drinking beer together. We were a tight group.
Kahle threw big parties for the design team at his house, nestled on the cliffs overlooking Lake Austin. Always a savvy investor, he built his house back in the 1980s before the rest of the world discovered Austin. The folks at his parties were rowdy and consumed lots of beer and margaritas. Kahle cooked his famous Kahle burgers,
delicious, if technically inelegant—thick, hearty, and smothered in cheese. Classic rock tunes from the 1960s and ’70s played in the background. There were generally two camps of folks at the parties: The first camp wanted to talk nonstop about work (shoptalk). They could pontificate ad nauseam about the details of their work. The second camp, which I belonged to, wanted to talk about anything but work. Both camps liked to drink a lot.
We were having so much fun, we didn’t even realize we’d awakened a sleeping giant. It took several years, but ultimately Intel crushed Somerset just as they did all of their competitors. Kahle fondly referred to those days as taking on the dark side.
There was a negative perception of Intel in the engineering world due to the technology giant’s monopoly of the PC microprocessor design space. On the software side, there was a similar perception of Microsoft, which dominated the software used on PCs. Microsoft and Intel, nicknamed the Wintel
pair for their combination of the Windows operating system and the Intel microprocessor, presented a formidable foe. Even facing that serious challenge, Somerset was still a fun and intellectually stimulating environment that Kahle and I both badly wanted to re-create in the STI Design Center—but this time, we meant to win.
The landscape of high-performance microprocessor design had changed significantly since those days in Somerset. Digital Equipment Corporation (DEC) and their once formidable Alpha microprocessors had disappeared. Sun Computer had lost a lot of their market share with their SPARC architecture. Supercomputer maker Cray Research had also gone by the wayside. Other minicomputer