The technology industry is still young, but its history is already rich with myths and legends.
The biggest myth is about how invention actually occurs – the notion of that “aha”’ singular, magical moment leading to inevitable success. The reality, as Malcolm Gladwell made clear in his New Yorker Creation Myth article several years ago, is that invention is more ponderous, with one idea building on another.
Within the technology industry, this cycle of invention is captured in eras, from mainframe and mini, to PC, Internet, mobile and the cloud. Most within the industry move from wave to wave, hoping to catch each successive one at just the right time.
Then there are the wave makers. The giants on whose shoulders the industry stands. Dave Cutler is a wave maker, with a broad set of shoulders.
Cutler, a Microsoft Senior Technical Fellow whose impressive body of work spans five decades and two coasts, will be honored Saturday evening as a Computer History Museum Fellow, along with Lee Felsenstein, the designer of the Osborne 1, the first mass-produced portable computer; and Philip Moorby, one of the inventors of the Verilog hardware description language. They join other wave makers such as Alan Kay, Vinton Cerf and Tim Berners-Lee in the museum’s Hall of Fellows.
“The Fellow awards recognize people who’ve had a tremendous impact on our lives, on our culture, on the way we work, exchange information and live. And yet, having had such a profound impact, they’re mostly unknown,” said John Hollar, the museum’s president and CEO. “People like Dave Cutler, who probably influences the computing experiences of more than 2 billion people, yet isn’t known in a way he deserves to be, in proportion to the impact he’s had on the world.”
Cutler, 74, who still comes to his office each day on Microsoft’s sprawling Redmond, Washington, campus, has shaped entire eras: from his work developing the VMS operating system for Digital Equipment Corporation in the late ‘70s, his central role in the development of Windows NT – the basis for all major versions of Windows since 1993 – to his more recent experiences in developing the Microsoft Azure cloud operating system and the hypervisor for Xbox One that allows the console to be more than just for gaming.
Steve Ballmer, Microsoft’s former CEO, is a fellow Michigan native, friend and golfing buddy. In his view, there isn’t another engineer who’s had a greater impact on the history of computing than Cutler. “There have been incredible visionaries who also made an impact, but not from the engineer’s seat,” Ballmer said. “I’ve never met another engineering leader with the same versatility, leadership and technical talents.”
Ray Ozzie, Microsoft’s former chief software architect, first met Cutler in the late ‘70s when he was a software engineer at Data General, a Digital Equipment Corporation (DEC) competitor. He considers Cutler one of the industry’s most preeminent and prolific engineers.
“The degree to which Dave has advanced the computing industry and advanced business can’t be overstated,” Ozzie said. “Dave’s groundbreaking work on VMS enabled DEC’s VAX to become the category killer in the era of the 32-bit supermini. When the PC itself then transitioned to 32 bits from 16, Dave’s work on NT was directly responsible for enabling Windows to yet again be the category killer. And as the computing world shifted from servers to services, Dave’s work on Azure was key to enabling Microsoft’s transformation to one of the world’s top providers of cloud computing infrastructure.”
Nathan Myhrvold, former chief strategist and chief technology officer at Microsoft, considers Cutler one of the greatest systems programmers of all time. “Writing hard-core systems software down in the bowels is a very specialized thing. For every systems programmer there are a thousand applications programmers who program on top of it. Dave’s just one of the greats.”
“If there’s one technical person who’s indispensable in the history of modern Windows, it’s Dave,” said Terry Myerson, executive vice president, Windows and Devices Group.
Cutler is a doer, not a talker. One of his favorite idioms is: “When all is said and done, much more is said than done.” So perhaps it’s best to have others put into perspective the impact he’s had on the computing experiences of billions of individuals and hundreds of thousands of businesses worldwide.
The Massachusetts miracle
In 1976, DEC was the darling of the technology industry. It and other competitors, like Data General and Prime Computer along the Massachusetts Route 128 corridor, ruled the computing landscape.
But Gordon Bell, the company’s top engineering executive, was concerned. Sales of the company’s flagship product, its 16-bit PDP-11, were stagnating and rival IBM was on the verge of releasing its first minicomputer.
Bell’s response: Change the playing field by introducing a new, 32-bit super-minicomputer line of systems called the VAX with a new operating system that would be backward compatible with the company’s PDP-11 programs.
Bell asked a 33-year-old engineer, who had joined the company four years earlier and made a name for himself by developing real-time operating systems for the PDP-11, to lead development of the VMS operating system. Forty-one years ago this month, Cutler and four other senior engineers launched the VMS project; Cutler was the senior programmer.
Bell, a founding trustee of the Computer History Museum who himself was named a Computer History Museum Fellow in 2003, said he chose Cutler to lead the development of VMS because “we both had the same goals and competitive urges … Dave is the ultimate competitor. He really wants to win.”
Two years later, the first VAX superminis emerged from DEC’s manufacturing plants and the VAX quickly gained a leadership position in the market. Bell would come to call Cutler “the best writer of operating systems in the world.”
Burton Smith is perhaps the best-known parallel computing designer and a Microsoft Technical Fellow. In the late ‘70s, he was working for a high-performance computing company and had the opportunity to meet Richard MacNeal, a founder of MacNeal-Schwendler Corporation, now MCS Software, the company that developed NASTRAN, a finite element analysis program.
“Dick took me over to this computer and said, ‘Look at this.’ It was a VAX 11/780 running NASTRAN,” Smith said. “Normally running NASTRAN on a new computer exposes bazillions of bugs and takes years to perfect. I said ‘How hard was this thing to bring up?’ He said, ‘Oh, it was a piece of cake. We just put it on there, compiled it and it started running.’ The impact of the VAX on the world had a lot to do with the fact that it was bulletproof. It was robust. It really worked as advertised. That was Dave’s work.”
While Cutler’s operating systems work on the PDP 11 and VAX are legendary, Bell is quick to add that the dynamic range of Cutler’s work at DEC is often overlooked. He cites three examples:
- The PL/1 compiler that included a backend runtime that ultimately hosted several other DEC languages (Cutler and others wrote a book on the work, “Engineering a Compiler”)
- The MicroVAX I architecture that Cutler helped design
- The DecCommand Language “that was really loved by all VAX users”
In 1982, Cutler met with Bell and announced he intended to leave DEC to form a company with a scientist from Lawrence Livermore National Laboratory. After meeting with Cutler and his cofounder, Bell made a counter offer, knowing how frustrated Cutler had become with the growing bureaucracy at the company’s headquarters at a former wool mill in Maynard, Massachusetts.
Bell told him, “Go anywhere you want to go, take anyone with you that you want, and do anything you want to do.” DECWest was born.
Cutler decided to locate his new operations more than 3,000 miles from DEC’s headquarters: in Bellevue, Washington, near Seattle and not far from Microsoft. Len Kawell was one of the young engineers who followed Cutler to set up operations there. “One day, Dave called me into his office and said, ‘Hey, I’m opening a new office in Seattle. You want to come with us?’ So I came out to Seattle in early ’80. We were originally just going to do a new real-time operating system for the VAX, but we ended up creating the MicroVAX and an operating system called VAXeln, which was a real-time operating system. Dave got into hardware at that point, actually designing the silicon, so Roger [Heinen] and I took over the software.”
One of the things that separates Cutler from other engineers, Kawell said, is his understanding of hardware. “Dave understands hardware like no one else I’ve ever worked with. A lot of people think in high-level language. Dave thinks in actually the registers and instructions of the machine. When we did the MicroVAX I, Dave wrote the microcode [a layer of hardware-level instructions] for the machine.”
In 1988, Cutler left DEC when his team’s Prism project, with its new Mica operating system, was killed.
Bell had first introduced Cutler to Bill Gates in 1983. Now, five years later, Cutler would join Microsoft to develop a new portable operating system, and create a new wave.
Rob Short had worked for DECWest since 1982. After DEC cancelled the Prism project, Cutler, two more business-oriented colleagues and he thought they might start a new company.
“But then Dave got a call from Bill Gates,” Short said. “That kind of freaked us out because we didn’t really have a high opinion of Microsoft at that point.” That meeting led to a follow-up meeting with Gates, Ballmer and Myhrvold.
“We had a fascinating conversation about where the industry was going,” Short added. “At one stage, I remember saying, ‘I don’t know what’s actually going to happen in the hardware world.’ And Bill said, ‘It’s not what we think is going to happen, it’s how we’re going to shape the industry.’ I had never met anyone who thought that way before.”
The courtship continued when Ballmer visited Cutler’s home one evening. “Steve came over to Dave’s house and when he left we looked at each other and said, ‘This is a different animal entirely. This is an interesting crowd of people.’”
Later that month, on Oct. 31, 1988, Cutler started at Microsoft. Short and other members of the DEC West team (five with software expertise, six with hardware) would soon follow. They provided their notices to DEC on a Friday and started the following Monday, recalled Darryl Havens, who would write the input-output system for NT.
The small, high-powered team of former DEC engineers and one existing Microsoft employee (Steve Wood) began by spending six months creating a specification for the operating system – the specification that now resides in the Smithsonian Institute.
“If you spend that amount of time designing something and you have a spec that gives you every single API [application programming interface], what its inputs are, what its outputs are, you pretty much know how the thing is going to work,” Havens said. “So I actually typed in the code for the entire I/O system in three weeks. That’s how well-designed it was. By the time I sat down to write the code, I already pretty much knew how it was going to work.”
The team started coding in earnest in April 1989, working double-digit hours six or seven days a week. The main goal: produce a portable operating system that could run on architectures other than Intel’s x86 chips and take advantage of the increased address space offered by nascent 32-bit microprocessors. RISC architectures were popular at the time and promised better performance than the x86. IBM and Microsoft had been cooperating on an operating system called OS/2, but it was a 16-bit operating system that ran only on Intel hardware and wasn’t portable.
The goals for the NT operating system were challenging and ambitious. The team had to make it:
- Portable and available on multiple targets (MIPS, Alpha, PowerPc, x64)
- Possible to run on multiple operating systems (POSIX (Unix), OS/2 and Windows 32
- Secure and C2 certified (a trusted computer certification)
- Run on systems with multiple processors (unique to the PC industry at the time) and capable of running multiple programs at one time, again unique to the PC segment
One of the toughest challenges was testing the system. Early on, the team decided it didn’t have the resources necessary to write a comprehensive test suite. Instead, they opted for a dynamic stress system, which put a severe load on the overall system. Every night the team ran stress tests on hundreds of machines. The next morning the team would arrive at the office, triage the failures and identify the bugs for the daily 9 a.m. bug-review meeting.
“It was a combination of very clever science and brute force and not being afraid of large numbers,” Short said. “There might be a thousand failures. So what are we going to do? Well, we started with one of them, looked at it and … Dave isn’t afraid of slogging through.”
The playing field kept shifting as well.
At first, the team was going to target the expanded OS/2 32-bit API as the main “personality” of the system, but later they changed to Windows 32 when Windows 3.1 proved to be so popular (16 million copies sold in six months). As a result, the team had to expand the Windows 16 API to a Windows 32 API and redesign the entire graphics subsystem. The team also had to hit the reset button on hardware when it changed its initial hardware target from the Intel i860 XR RISC processor to the MIPS R3000.
Another particularly vexing problem was getting DOS and Windows 16 applications to run in the new 32-bit environment.
“We wanted to write a modern operating system from scratch,” Myhrvold said. “We also wanted to have some level of backward compatibility with previous systems and that’s where everything was difficult. But we came up with a variety of methods to do it, some in my group, some in Dave’s … It’s always hard to have backward compatibility when you’re doing something brand new and you’d love to throw the whole past out. But for customers it’s really important to have that bridge to the past. Figuring out how we could do that so that existing Windows applications could get moved over and run on NT was pretty important.”
Myhrvold recalls that the teams had a strategy for handling DOS apps, but Windows apps presented a greater challenge. “But we made it work,” Myhrvold said. “Without that, I don’t think there would have been much of a future for Microsoft.”
“What Dave and team accomplished was an almost impossible design challenge,” said Ed Lazowska, the Bill & Melinda Gates Chair in Computer Science & Engineering at the University of Washington.
Bell believes Cutler is the only engineer with the confidence to pull off NT as he did. “Almost anyone who would have been good enough to do NT would have insisted on a blank sheet for the spec,” Bell said. “Dave appreciates legacy and compatibility. The world is better off because Dave Cutler went to Microsoft and built NT for a much larger market.”
In 1988, when the project first began, the team comprised about 20 engineers. By the time the first version of Windows NT shipped five years later, the team had expanded to about 150 engineers as it battled constraints and tradeoffs.
Windows NT 3.1 shipped on July 27, 1993. The team was exhausted, but exhilarated.
“People work for Dave because they know the project is going to succeed,” Short said. “Dave is intense. He can be crude and demanding at times, but that’s actually a small piece of him. He’s actually very good at motivating people . . . . If you’re an engineer, you want to work on a project that you think is useful. You want to think that the project will succeed and that your individual effort will make a difference. When you worked for Dave, you were in a project like that.”
Part of Cutler’s secret sauce is that he inspires a loyal crew around him, Myhrvold said. “He’s quite a character…Did you see the movie “Inglourious Basterds”? There is a whole genre of old World War II military movies about this great commander who has this loyal set of guys and Quentin Tarantino updated it. When I saw the movie I said, ‘Hey, this is Dave,’ Myhrvold said, laughing. “There are probably worse things than comparing a man to Brad Pitt.”
Cutler stopped managing the entire NT project in 1996, but continued to lead the kernel development until 2006. In March 2005, he completed one of his “most gratifying pieces of work” at Microsoft when, partnering with AMD, he helped develop the AMD64 architecture (64-bit extensions to the 32-bit x86 architecture) and led the effort to ship the first two x64 64-bit Windows systems (workstation and server). At the time, some questioned why Microsoft developed a 64-bit system; today most computers are 64-bit systems and even our phones will soon have a 64-bit operating system.
In 2008, Cutler was honored at a White House ceremony as one of the nation’s National Medal of Technology and Innovation Laureates. In support of Cutler’s nomination for the award, Bill Gates provided evidence of just how hard the task had been:
“… NT is unique because it lives within the constraints of ill-defined hardware, while providing a runtime environment for the myriad of legacy applications that ran on the loosely defined PC Windows operating systems of the early 1990s. Unlike other systems, he built a compatible, yet many-way scalable system that hosted multiple environments. Dave was the principal designer of the layering structure that ensured only a few components needed to be changed to run on either a different instruction-set architecture or on machines with radically different hardware and input/output subsystems. In 1989, NT was originally designed to be OS/2 and POSIX compatible. The Windows subsystem was added without core design changes. NT runs on a range of systems from gas pumps to 64-CPU 64-bit systems with more than a terabyte of memory, including clusters. With the introduction of Windows XP in 2001, it became the basis for all Microsoft PC-based operating systems.”
Ballmer’s viewpoint is more succinct: “There wouldn’t be a Microsoft today without Dave.”
Moving to the cloud
In 2006, Amitabh Srivastava was a corporate vice president in Microsoft’s Windows division, working on redefining the organization’s engineering processes. Ozzie had recently been named the company’s chief software architect and the two had their first meeting one late afternoon in Building 34 on Microsoft’s campus.
Srivastava has always had a rule: If he’s in town, he never misses dinner at home with his family – or if he needs to, he tells his family he’ll be late. That evening, Srivastava lost track of time. He missed dinner and never called home to say he’d be late. The one-hour meeting began at 4 p.m. and went until 8 p.m.
“By the end of that meeting, I was convinced software wouldn’t be shipped as it had been. My personal realization was, ‘I’m working on the wrong thing,’” Srivastava recalled.
At the time, Srivastava’s office was across from Cutler’s, and the two often got to the office early. Soon after the meeting with Ozzie, Srivastava recalls telling Cutler, “I don’t know what needs to be done, but I know there’s something changing dramatically and we’ve got to rethink our approach.”
After a few more weeks of discussions, Srivastava knew Microsoft needed to build an operating system for the cloud, and he identified his first task: Recruit Cutler.
“So I go to Dave and he says ‘I think I’m ready to retire,’” Srivastava said. “I said, ‘Dave, not quite. This is different. This could change the world.’”
Cutler didn’t say yes to Srivastava, but he also didn’t say no. “I had worked with Dave long enough to know that when he didn’t say no right away, that was a good sign.”
Srivastava developed a plan for Cutler and him to visit every team at Microsoft running a cloud service, from MSN and Hotmail to Xbox Live and the company’s cloud data centers. “This is the same guy who won’t go to meetings. Dave went to every meeting.”
The due diligence process took a few months as Cutler and Srivastava listened to the pain points and band-aid approaches teams had taken to keep their cloud services running. After the tour, Cutler and Srivastava never had a formal discussion about him joining the team. Cutler was on board.
“We never had a problem recruiting,” Srivastava said. “Once Dave was there, the Red Dog (the project’s code name) team was the one everyone wanted to work on.”
Cutler’s role was to develop the hypervisor for the cloud operating system. “Dave wrote the hypervisor; it’s probably the most efficient you could think of. It was completely optimized. We knew that any part Dave wrote would be the best,” Srivastava said. “Dave’s just a phenomenal guy. He’s brilliant. His work ethic is amazing. And he has a very high bar for quality; Dave doesn’t cut corners.”
Two years later, on Oct. 27, 2008, Ozzie stood on stage at the company’s Professional Developer’s Conference in Los Angeles and announced a technology preview of Windows Azure (now Microsoft Azure).
“… Amitabh, Dave and their team have been working for a few years now on our own platform for computing in the cloud,” Ozzie said. “It’s designed to be the foundation, the bedrock underneath all of Microsoft’s service offerings for consumers and business alike, and it’s designed to be ultimately the foundation for yours as well. And so I’d like to announce a new service in the cloud, Windows Azure.”
Srivastava followed Ozzie on stage, wearing his Red Dog sneakers, and said: “It’s my pleasure to finally discuss Windows Azure, our Project Red Dog that Dave Cutler and I have been leading quietly for some time. Dave is a kernel guy and what you have there is the kernel of the Microsoft Cloud Platform. Kernels don’t demo well. They don’t have the glitz, or the glitter, but a good one allows others to create killer apps, and that’s exactly what we have done. We have built a platform to allow you to build your killer apps.”
Eight years later, Microsoft Azure plays a significant role in Microsoft’s cloud business. At the company’s most recent developer conference in San Francisco, Scott Guthrie, the company’s executive vice president of its Microsoft Cloud and Enterprise Group, told developers Microsoft’s cloud now manages more than 1 million servers within 30 unique Azure regions around the world. “To put that in perspective,” Guthrie said, “that’s more locations than Google and AWS combined.”
After the conference, financial analysts for Sanford Bernstein wrote an investor report with the headline: “Quick Take – The Microsoft Build Developer Conference – All Roads Lead to Azure?” Within the report the analysts said, “Azure is increasingly the center of all of Microsoft’s development and product strategies. After numerous conversations at the Build 2016 Conference, we’re feeling even more confident in the Azure opportunity and the potential that Azure could grow very fast for an extended period of time.”
Separating the best from the rest
In 2011, Boyd Multerer, the then-director of development for Xbox One, had a problem. Multerer, who helped create Xbox Live, the gaming and entertainment service, and the father of the popular XNA video game programming language, had decided with his team that Xbox One needed a virtual machine if both games and apps were going to run on the console.
The initial thinking was that it might be too hard to work.
“We weren’t sure we could do it,” Multerer recalls. “We knew we would need someone really special to pull it off. So we asked ourselves, ‘Well, do we know anyone who could do this type of specialized work’ and Dave’s name was about the only one that came up. He’s got that depth of knowledge at the bottom of the operating system – how it interfaces with the hardware, how you build virtual machines. All that experience was there, but he’s legendary and intimidating, so we figured there’s no way we’d ever get him to join our team.”
Hoi Vo, a distinguished engineer on Multerer’s development team, knew Cutler, having worked with him on Microsoft Azure. He helped broker a meeting for Multerer, Cutler and himself in a “neutral” building on Microsoft’s campus, away from both the Xbox and Azure teams.
“It was probably the scariest meeting of my life,” Multerer said, “just the anticipation of it.”
Multerer and Vo walked Cutler through their plans for Xbox One. Cutler sat silently through the entire meeting, never asking a question. When the meeting was over Multerer recalls thinking, “OK, I have no idea how that just went.”
A couple days later, Cutler communicated to Multerer and Vo that he wanted to learn more. Soon they set up a second meeting with the team’s distinguished and senior engineers. The team was “scared to death,” Multerer recalls. In the meeting, each engineer explained what she or he was doing, talking about the importance of performance, predictability and robustness.
Soon after, and a few months before his 70th birthday, Cutler joined the team. He soon “set the bar for how hard people should work and how high they should hold the quality bar,” Multerer said. Two years later, on Nov. 22, 2013, Xbox One shipped in North America.
“Dave designed and wrote the hypervisor for Xbox One,” Multerer said, with an obvious sense of awe. “He wrote the entire bottom of the stack. Because the hypervisor is there, Xbox games can run on Windows. That’s why apps run on Xbox One. The impact of that work is phenomenal. And the amount of work he did was phenomenal.”
Having the opportunity to see Cutler work as an individual contributor, collaborating closely with a small number of other engineers on his team, Multerer got an opportunity to see what separates the best from the rest.
“Dave fits a pattern that I’ve seen from the very best software engineers,” Multerer said. “They have similar traits, one of them is you hold quality extremely high. The best engineers like Dave are fanatical about quality. That means they write a lot of test code. They ensure that the code they write works. That’s what they hang their pride and reputation on. Most software engineers measure their success in terms of volume of code. The greats like Dave measure themselves in terms of quality of code – small amounts of quality, tuned, performant, robust code that doesn’t crash … It’s that fanatical embodiment of code quality that separates Dave from the rest. He just won’t accept anything less, from himself or others.”
Multerer laughs, recalling a story to make his point. Jon Lange, who wrote the memory manager for Xbox One and worked closely with Cutler, was bouncing around the office one day, obviously extremely pleased. “I think it was one of the happiest days of his life,” Multerer said. “He found a bug in Dave’s code and Dave said ‘Yeah, you’re right. We need to fix that.’ That made Jon’s day.”
Valerie Chen is an 18-year-old high school senior at Thomas Jefferson High School for Science and Technology in Alexandria, Virginia. On a recent Saturday in March, she and three other high school seniors were in Seattle, being honored at the Living Computer Museum.
Chen, Matthew Edwards from Blacksburg High School in Blacksburg, Virginia, Karthik Rao from Briarcliff High School in Briarcliff Manor, New York, and Cherry Zou from Poolesville High School in Poolesville, Maryland, became the first recipients of the Association for Computing Machinery (ACM) and Computer Science Teachers Association (CSTA) Cutler-Bell Prize in high school computing, funded by a $1 million endowment established by Cutler and Bell. Each winner received a $10,000 prize.
The four students presented their projects to Bell, Cutler and Jeannette Wing, a Microsoft corporate vice president of research, among others from ACM and CSTA.
Chen, who will be attending Yale in the fall as a computer science major, loved the fact that Cutler, Bell and Wing toured the museum with them, showing the students artifacts of systems they had actually built. “That was really amazing,” she said. “It was really great that when we presented our projects to them they understood and appreciated the work. It felt really good to have someone recognize our work.”
In return, the students provided Cutler and Bell some advice on how they could better use social media to publicize the prize among high school students.
There certainly are more computing waves to come; Bell and Cutler want to ensure that the next generation of engineers is prepared to make and ride the waves.
“Gordon and I wanted to start something at the high school level that would focus on getting more students interested in computer science early,” Cutler said. “This year’s recipients were outstanding. Our hope is that other institutions and companies will see the merit of this approach and donate funds to further the scope of the awards. The initial recipients of the award reinforced our conviction that this is a very effective way to foster the advancement of computer science.”
The Cutler-Bell award might encourage future generations of engineers to pursue opportunities in augmented reality or quantum computing, but Cutler already has impacted generations of engineers, Ozzie insists.
“One of Dave’s unspoken contributions is that he has created generations of incredibly strong engineers, simply as a side-effect of being who he is and doing what he does,” Ozzie said. “Speaking from personal experience from back in the ‘70s and ‘80s, those who worked for him – such as Tim Halvorsen and Len Kawell, my cofounders in the startup that created Lotus Notes – were taught a very specific engineering rigor. They learned about coding and commenting conventions, source code and project organization conventions, and so much more. There was only one way to do things ‘right’ and ‘optimally,’ and it was intensely rigorous. He taught them. They taught me. I taught others. Generations have learned rigorous methodology, and have become far better engineers, even without having directly worked with him.
“The companies and products he benefited will come and go,” Ozzie added, “but the culture of engineering excellence that he created, above all, is his lasting legacy.”
Bell won’t be able to join his friend of more than 40 years at Saturday evening’s event at the computer museum. He’s traveling. Asked what his toast to Dave would be if he could be there, Bell responds: “Hey Dave, just keep on keeping on.”
Cutler intends to do just that. On Monday morning, he’ll be back at his Studio A office at Microsoft, because he’s a thinker doer, not a talker.
His advice for Valerie, Cherry, Matthew, Karthik and forthcoming generations of software engineers?
“I’m a great believer in Fred Brooks’s taxonomy of people,” Cutler said. “He said in his book, “The Mythical Man Month,” that there are thinkers, doers and thinker doers. Thinkers are a dime a dozen. Anyone can think and profess great ideas. Doers are more valuable because they do things and get things done. The most valuable, however, are the thinker doers. They think and they do!
“Much of my success belongs to the people I have worked with,” Cutler added. “Every project I have worked on has been filled with industry-leading software and hardware engineers. My part in relation to theirs has been quite small.
“But I have always strived to be a thinker doer,” Cutler continued. “I have a couple of sayings that are pertinent. The first is: ‘Successful people do what unsuccessful people won’t.’ The second is: ‘If you don’t put them [bugs] in, you don’t have to take them out.’ I am a person that wants to do the work. I don’t want to just think about it and let someone else do it. When presented with a programming problem, I formulate an appropriate solution and then proceed to write the code. While writing the code, I continually mentally execute the code in my head in an attempt to flush out any bugs. I am a great believer in incremental implementation, where a piece of the solution is done, verified to work properly, and then move on to the next piece. In my case, this leads to faster implementation with fewer bugs. Quality is my No. 1 constraint – always. I don’t want to produce any code that has bugs – none.
“So my advice is be a thinker doer,” Cutler concluded. “Focus on the problem to solve and give it your undivided attention and effort. Produce high-quality work that is secure.”
Words to live by from a man who, when all is said and done, has done more than he’s said.
Watch a short summary of Dave Cutler’s contributions to computing. This video will be shown on Saturday at the Computer History Museum Fellow Awards Gala just before Cutler is inducted to the Hall of Fellows. ©2016 Computer History Museum.
Visit computerhistory.org to learn more about the Computer History Museum Fellow Awards.
Lead photo credit: Scott Eklund/Red Box Pictures