The interviewer, Dave Plummer, is also is also an amazingly interesting person in his own right. I particularly enjoyed his retro-coding videos, such as <a href="https://www.youtube.com/watch?v=JlZe2JwrJqM">https://www.youtube.com/watch?v=JlZe2JwrJqM</a> and <a href="https://www.youtube.com/watch?v=b0zxIfJJLAY">https://www.youtube.com/watch?v=b0zxIfJJLAY</a><p>The videos are really interesting and his background muzak and RGB lighting puts me in a Christmas mood. He generally put Microsoft in a completely different light than I'm used to, he speaks warmly about his job, co-workers and Microsoft, while acknowledging much of the weirdness going on in Redmond.<p>Only problem is that watching is channel will trigger something in the YouTube algorithm and flood your feed with videos on ADHD. Presumably it has to do with his videos on autism and ADHD, but I feel like YouTube should be smart enough to notice that I didn't watch to videos, only those on coding and Microsoft history.
I haven't watched this video yet but I'm looking forward to it, having read Showstopper[1] quite a few years back.<p>One thing that stuck out to me when I was still in my early 20s thinking I needed to work all the time was the mention that Dave would always take holidays on time, every time without any debate.<p>While I may not love Microsoft, it was probably my first real exposure of a highly competent and qualified person who wasn't grinding 24/7.<p>It still feels nuts to write it but it's a holdover from rural (and retail) life where the mindset is basically "The more you suffer, the more virtuous you are".<p>As much as I still struggle to properly take time off (that is, it's easy to postpone because of X or Y being more important), thinking about Dave's view is always a good reminder that it's not a choice between taking a break and being good at X.<p>[1]: <a href="https://www.amazon.com/Show-Stopper-Breakneck-Generation-Microsoft/dp/0029356717" rel="nofollow noreferrer">https://www.amazon.com/Show-Stopper-Breakneck-Generation-Mic...</a>
Near the tail end of WinNT 3.1 development, I read an article (possibly from Usenet) about someone creating a screensaver that showed a bluescreen.<p>I had never created a screensaver before.<p>I could reliably cause my WinNT dev box to bluescreen due to a bug in an internal Microsoft network driver.<p>So I read the docs for writing a Windows screensaver. After writing down the values shown for my bluescreen, I cobbled together my first and only Windows screensaver.<p>I sent an email to the Windows NT group announcing my creation for laughs and giggles.<p>A few weeks later, the NT build group decided to play a prank on Dave Cutler.<p>They installed my bluescreen screensaver on one of their build servers.<p>They also unplugged the mouse and keyboard from the build server.<p>Then they waited...<p>Dave Cutler comes in to check on the status of the latest NT build.<p>He turns on the monitor and sees a bluescreen.<p>He tries moving the mouse.<p>Nothing.<p>He tries typing on the keyboard.<p>Nothing.<p>Then the unanticipated happens.<p>He reaches over and pushes the power button on the build server to reboot the build server.<p>NOOOOOOOOOOOOOOOOOOOOO.<p>I never heard about the aftermath/any fallout from their prank.<p>With great power comes great responsibility.
I’ll recommend here the book “Showstopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft”, which someone else recommended a few weeks ago. Link:<p>I’m still reading it, but it’s really enjoyable. And it makes me wish I had been part of that history. Particularly the whole thing about dogfooding a brand new OS. But it caught me a few years too early.
The bit I found interesting was how Xbox's hypervisor is based on that of Azure, rather than anything they did on the desktop, and that Xbox games are/were packaged up with an OS rather than relying on a single OS on the device, so a bit more like containers. Dave also said he's working on making ML workloads run on idle Xbox Cloud Gaming devices. Any architectural tie between Azure and Xbox had never occurred to me before.
I worked in the windows kernel team and my favorite story about DC is when he basically made x64 happen because he hated Itanium architecture so much. He worked with AMD and basically made it happen while cranking in his corner office.
One of the most pivotal moments in my software engineering career came from reading the leaked NT source code (6-7 years ago) in conjunction with reading the Showstopper[1] book. The NT leak is particularly fascinating because it included all of the author history, so you can see exactly what files Dave Cutler worked on. The book goes into detail about how we ended up with things like kernel modules having pageable sections -- which is fascinating in its own right.<p>The book describes Cutler coming in and revamping certain assembly routines and you can see exactly what routines are being talked about in the actual source code.<p>Cutler's code was (and I'm sure still is) absolutely beautiful C code. It really impacted the way I write NT-style C code.<p>[1]: <a href="https://www.amazon.com/Show-Stopper-Breakneck-Generation-Microsoft/dp/0029356717" rel="nofollow noreferrer">https://www.amazon.com/Show-Stopper-Breakneck-Generation-Mic...</a>
The Computer History Museum oral history interview with David Cutler is also very good:<p>Part 1: <a href="https://youtu.be/29RkHH-psrY" rel="nofollow noreferrer">https://youtu.be/29RkHH-psrY</a><p>Part 2: <a href="https://youtu.be/SVgSLud50ss" rel="nofollow noreferrer">https://youtu.be/SVgSLud50ss</a>
Looking back on all both Daves said, there is an extraordinary amount of attention paid to getting things done and out the door, and almost no mention of planning ahead, and actual security strategy. Its all commercial pressure to get the sausage out of the meat grinder, and keep the failures down to an acceptable level.<p>No wonder things never get better, and never take a turn in the right direction, industry wide. I used to think we'd eventually get to capability based security, but now I see we'll always be stuck with application permission flags, the almost worthless bastard cousin, instead.<p>I weep for the future.
Looking forward to listening to all of this.<p>Regardless of you feelings towards him or the company he works for, Cutler has been a very influential software engineer through his work on OpenVMS and Windows NT, and I don't think he's talked about as much as the Bell Labs gang, Stallman, Linus, Stroustrup, and so on.
Cutler: ...Microsoft had DOS which was pathetic...
Dave: .. I wrote some of that!<p>That was hilarious. I still remember how good NT even though it struggled in my 486 with 4Mb of RAM, Dave Cutler is a legend.
I was hoping to get some insight into the roots of NT. At the time my understanding was that it resulted from the split between IBM and MSFT and that MSFT was already developing NT based on their derivative of OS/2. That was IIRC before Dave Cutler went to MSFT.<p>Later on that (OS/2 -> NT) seems to have been scrubbed from history and NT is now derived from VMS. I'm curious where the truth lies.<p>It was well documented at the time that early NT error messages occasionally identified themselves as OS/2.<p>I'm over an hour in and not sure how close I'm getting to that. At about 1:09:00 Cutler states that they "developed NT on OS/2" but I think he meant their toolchain was hosted on OS/2 (and they couldn't wait to get off of it.)
I knew someone who worked on the Windows kernel in the "aughts". Apparently, Dave Cutler was still looking at kernel code reviews back then, and could be quite unsparing in his feedback.
Not a fan of MS as a business.<p>But the tech that built the business is fascinating. Surprised to see an 81 y/o still working. Dude looks good.<p>Haven’t fully watched the episode (3hrs long!). But it’s queued.
I keep meaning to try ask Bill Gates this question whenever he does one of his Reddit AMAs:<p>Bill, what are you most proud of out of the following two:<p>1. Getting Cutler to come over from DEC and spearhead NT.<p>2. Committing to backwards compatibility early on, that ensured old apps Just Worked on new versions of Windows.<p>I don’t think Microsoft would look like it currently does without either of those two historical paths taken.
I finally plowed through the computer parts of this interview.<p>This tells you so much about how Microsoft works they probably will want it removed from the internet. Not directly but implicitly between the lines.<p>My conclusion is that what built our winners today is just infinite amounts of energy and random selection until something stuck to the wall.<p>Complete bat shit ranges of bit sizes and competing infrastructure (you cannot compete with infrastructure because uniformity is the main driver)!!!<p>This is not a technique we will have the luxury of using from now on.
Was the origin of 'NT' in 'Windows NT' really New Technology? Some suggest that the name might have originated from the Intel i860 CPU. Originally, NT was targeted at the Intel i860 CPU, codenamed N10 (or "N-Ten"). Dave Cutler's put to rest that it was 'New Technology' <a href="https://www.youtube.com/watch?si=2ZCM44xPTR831MeR&t=4233&v=xi1Lq79mLeE&feature=youtu.be">https://www.youtube.com/watch?si=2ZCM44xPTR831MeR&t=4233&v=x...</a>
I've been watching Dave's garage for a while now and really love it. The combination of new projects and "war stories" as well as his personality ticks all the boxes for me.
The Smithsonian has a copy of the “NT OS/2 Design Workbook” by Cutler and others on the team. I don’t think there’s a piece of technical writing I’d more like to read.<p><a href="https://americanhistory.si.edu/collections/search/object/nmah_742559" rel="nofollow noreferrer">https://americanhistory.si.edu/collections/search/object/nma...</a>
This is fascinating in so many respects. One is it is almost like his whole career developed through a series of events attempting to escape the usual bureaucracy of successful companies.
The correct link is <a href="https://www.youtube.com/watch?v=xi1Lq79mLeE">https://www.youtube.com/watch?v=xi1Lq79mLeE</a>
For those who misread the title as I did, this is not Dave Coulier. Moreover, it is not Dave Coulier wearing stonewashed jeans and a mullet, making Full House era jokes, in a forgotten Microsoft promotional video about Windows 95.