B (10:19)

I do. I didn't own my first computer for a long time, but the first computer I ever used was a TRS 80 model 1 level 1 4K machine. And I rode my bike in 5th or 6th grade. So I was about 11 to the local Radio Shack and you know, they had the standard component stereo systems and everything else the Radio Shack had, but they had a stack of boxes that was labeled computer. And so I was asking the people that worked there about it and they said they just got it and they hadn't set it up yet. And so I was rather precocious and I figured, well, I'll set it up for you. And they said, okay, have a shot.

A (10:47)

Did you know what you were doing?

B (10:48)

Absolutely not. I mean, it's no worse than a component stereo. The only thing is that Tandy and their infinite wisdom used the same five pin DIN connector for power, video and I think cassettes. So they're all I identical and if you plug them in wrong you'd blow it up. So I read the label and got it working and wound up playing with it and not knowing anything about computers. So I'm typing English commands into it and you know Print two plus two works perfectly. Yet more simple English that you enter into A basic Level 1 interpreter is not going to get you very far.

A (11:17)

So you're trying to talk to it in English.

B (11:18)

Yeah, didn't know any better. And I still have an old full scap that I wrote in sixth grade of a program that's kind of logically correct but has no chance of working on any interpreter that existed at the time. So it took me a while to figure out what was actually going on with them. But I rode my bike down there every Thursday and Saturday and they graciously let me use the machines.

A (11:38)

When was this?

B (11:39)

79, 80.

A (11:40)

Okay. What was the state of the art of computing back then? So what are we talking about?

B (11:44)

Well, the big three had come out, there was a TRS 80 model one, there was the PET 2001 and the Apple II came out roughly simultaneously.

A (11:52)

Apple II, would you say that's the greatest computer ever built?

B (11:56)

Probably, in retrospect? Well, I would probably give that to the Commodore 64.

A (12:00)

Yeah. You and I agree on this. That was my first computer, probably many years after it was released. But yeah, Commodore 64 is incredible. But yes, Apple II had a huge impact on the history of personal computers.

B (12:12)

Right. It's hard to gauge the long term impact, but I think the 64 itself probably influenced more people. So that's my reason for picking that one.

A (12:20)

You think so?

B (12:20)

The sales are certainly higher.

A (12:21)

So Commodore 64 sold a lot?

B (12:23)

Yeah, I mean, the numbers are hard to believe. It depends which numbers you believe, but even the medium estimates are pretty high.

A (12:30)

All right, cool. So you eventually graduated to the Commodore 64. Tell me about that machine. What did you do on the Commodore 64?

B (12:38)

Well, the first thing I did was overheat the floppy drive on it, which was unfortunate because it wasn't a warranty machine. My parents didn't have a lot of money, so we bought it from Computer House as opposed to one of the major retailers, which meant when it died it had to go back to Germany or something to be fixed. So I was left with no floppy. And so I had a cassette deck, which was the best you could do at the time. And so I was writing small things and I had a machine language monitor that you could load from cassette. Didn't have an assembler built in, but had a disassembler so you could enter the opcodes in 6502 min hex. And if you were careful about planning, you'd be able to write some basic programs. So that's kind of How I learned. And the first thing I ever wrote on it was a clone of Galaga. Now it's a bad clone of Galaga, but it has the major enemies that attack over time. And it's all written in hand coded machine language. And you can't relocate 6502, so if you need to add code in the middle, you need to manually sort of jump to somewhere else, do your work, jump back to where you were. It's just hideous spaghetti code. But it all worked eventually and I went to make a backup of it to preserve it for future scholars or whatever the hell I was doing. And I copied my blank floppy onto my data floppy. So that was my first experience with data management. And so I don't have a copy of my first program anymore.

A (13:48)

What was that feeling like? Do you remember? Of just doing something, if I may say so, like stupid, you know, which is a part of the programming experience.

B (13:57)

Yeah. There was a huge amount of guilt because. Right. You destroy several weeks of work and you know, it was because you rushed or you did something stupid or you made an unwise choice.

A (14:06)

Wait, can you tell me about the programming involved in that?

B (14:09)

So it's literally machine language.

A (14:11)

So machine. So it's not even assembly.

B (14:13)

Not assembly yet, because there was no assembler built in. So I should have read an assembler, written an assembler as my first task, but I wasn't that clever.

A (14:20)

So how hard is that to do?

B (14:22)

Trivial. And it's just one of those things that sticks. I think you do so many times. You know, if I give you a C issue, there are certain syntactic issues in C that you're never going to forget and get wrong.

A (14:32)

Yeah.

B (14:32)

And it's just one of those.

A (14:34)

What are the limitations of programming in machine code?

B (14:36)

As a programmer, the biggest issue is you have to write completely sequentially because at least in that variant 6502, you can't add things later, you can only add things on the end. So it's like programming a tape in a way.

A (14:47)

What was the most complicated thing you've built with machine language?

B (14:51)

That game would be. I mean, in assembly language I've done a fair bit of complicated stuff, but in actual machine language, I think that game would be the only thing I've.

A (14:58)

Actually literally built a game.

B (14:59)

Not a great game, but it worked okay.

A (15:02)

All right. And then you erased it.

B (15:03)

I did.

A (15:04)

All right. When did you first fall in love with programming? When you figured out like, this is a. This is something special.

B (15:12)

I think there was two stages for me. I always Knew immediately that I was fascinated with these machines from the TRS 80 Model 1. That's all I wanted to do, is ride my bike back there and have more time with it. And I did that, you know, to wear out my welcome as much as I could. And the other revelation came, I think about second or third year university when I realized I love programming, but I have no idea what I'm going to do. Am I going to make the 12 flash on a VCR somewhere or am I going to go work on an operating system? I have absolutely no idea what I'm going to do post graduation. But I love what I do. And so I think that was a lot of consolation. It's like it doesn't really matter what I'm doing at this point because I kind of love doing it.

A (15:47)

So you'll figure it out.

B (15:48)

Yeah.

A (15:49)

As long as you're following this kind of feeling.

B (15:52)

I knew I was in the right area finally. Yeah.

A (15:54)

All right. You dropped out of high school.

B (15:56)

Yeah. Not the smartest move.

A (15:57)

Okay. But you ended up going back to school and being very successful at school and just in general successful as a programmer, as a developer, as a creator of software. How were you able to find your way? Can you tell that journey of dropping out and then finding your way back.

B (16:15)

There's no moment when I dropped out. You just go less and less and less until you realize it's going to be embarrassing if I show up because I haven't been there in a long time. And then pretty soon you're just not going. And that's how you drop out of high school. So if you find yourself on that path, stop doing that. But that's precisely what I did. And so now I'm not at school and I have to get a job. So I'm working at Seven Eleven and a paint warehouse and stuff like that. And Seven Eleven is actually kind of an interesting job because it's a job I think they keep rotating for people that are smart enough to do the night shift with all the accounting and the administration and stuff they make the night shift do, but that have reasons personally that they need to work at 7:11. And I was one of those people because I had no high school diploma.

A (16:54)

What are some memorable moments from that time at 7:11? Maybe what do you appreciate about the difficulty of that job?

B (17:02)

Probably the worst moment for me, I mean, I got held up at knifepoint and stuff. And that's all entertaining, but the worst, the most, the suckiest part for me was doing the gas dips. You've got a long, it's like a 15 or 20 foot wooden stick and it's measured in gradients of inches and feet. And you drop it into the gasoline tanks and then you bring it up and you measure where the gasoline sits because there's no electronic sensor. So I'm doing that and the first time I do it, I drop the pole and I re grab it. Well, that's about a thousand splinters of wood into your hands and it's 40 below out. And that really sucked.

A (17:32)

Oh, wow.

B (17:34)

I realized I don't want to do this for a whole life. I knew that.

A (17:37)

So, okay, so you stand there frozen with splinters in your hand and at.

B (17:42)

Some point I have a revelation about my life. That next time I'm going to do it differently. And then how ludicrous that is hits me about three seconds later. Right. And I think that was really the moment for me where I realized that I've got to do something different. And so even though I was 21, I went and I talked to the principal of my local high school and I was like, can you let me back in? And he's no, you're too old and we don't have room. It was his main reason. And I said, well, between now and then somebody's going to drop out, so you'll have room. So let's assume you have room. Can I come back? And he was gracious and let me come back. And so I did the three or four classes that I needed.

A (18:18)

Yeah, you know, just if you can linger on that, the slow dropping out, that's a weird thing that you can do with your brain. You realize to yourself that you don't have to do the thing that everybody else is doing. And that's a dangerous realization because like you kind of have to, to be part of society, do certain things.

B (18:38)

Right.

A (18:38)

And if you realize like you don't have to do what everybody else is doing, you, you can either have an incredible life or a really difficult life.

B (18:48)

Well, the problem with that process is you're making a much smaller decision. I'm just not going to go to class today. And that's all you're deciding. But you do that enough times, you're making a much bigger decision and that's the problem.

A (18:58)

So it's better to make. If you want to live life in a non standard way, it's better to make the big decision explicitly and then you can stop going. Yeah, don't allow yourself to make the.

B (19:09)

It'll be made for you eventually.

A (19:11)

Okay, well you got back and you eventually went to college and were very successful as a student and you weren't that good of a student before.

B (19:18)

No, I was a terrible student in high school and even my first semester of college I still wasn't taking it quite serious because I got Mercy passed in geometry 90 which is like the makeup class for the geometry 12th grade class that I didn't have. And that scared me because I realized by 1% or the grace of the professor that let me through. I just about ended my entire university career here. So fortunately those marks don't count on your transcript because of remedial classes. And so I got kind of a fresh start the next semester and did it for real. I did it for me and that made all the difference.

A (19:49)

What can you speak to maybe by way of advice on how to be successful as a student?

B (19:53)

Well, ideally there's some aspect of school that you do enjoy, whether it's art, whether it's computer science, whether it's shop class, whatever. So go for those classes and just put up with and do the hard stuff because it's way easier than having to do it later. And that's easy to say when you're 50 something. It's harder to say when you're 15 something, but it makes a lot of sense.

A (20:14)

All right, what's the story of you joining Microsoft? How do we get to there from 711 to Microsoft?

B (20:21)

Yeah, it's a big jump. So I had gone back to school and I think it was my third year of university. I was working for the phone company for the summer as a summer job and I'm doing conversions of their UB NET to TCPIP and modern networking which really a mess through swapping cards but then figuring out why their config sys doesn't allow Lotus to run anymore because it's got 10k less than it used to and it's just a horrible time to be working in computers. But I was doing it. And at lunch I'm sitting in the food court with the old and the bored and I'm reading a book that I had bought called Microsoft or Bill Gates and the Making of Microsoft Hard Drive I think is his title. And it's a great book. It's just sort of a matter of fact history of how Microsoft came to be. What it's like, how it operates, what the people are like. There's. And I'm reading this book and I become really entranced by it and fascinated because it sounds like exactly the place that I want to be. But I'm in Saskatchewan. So what am I going to do about it? And what I wound up doing was I had put myself through school with a program called hypercache, which is a file system cache for the Amiga, because the Amiga didn't have any out of the box and it had done reasonably well. And so I went through my registration cards, because in those days you had a 4x6 card that people would fill out with their name and their address and if they had an email, their email, and they send it in, they get notifications of updates and so on, when it's shareware. And I went through the whole stack looking for anybody with a Microsoft email address and I found maybe three or four people. And I just cold emailed them and said, hey, I'm a operating system student in Saskatchewan looking for an opportunity. I don't remember exactly what I said, but one guy, Alistair, Alistair Banks, he wrote back and he said, I know somebody that I can put you in contact with. And he put me in contact, I think, with a guy named Ben Slivka, who did a phone interview, who eventually wound up hiring me to work in Ms. DOS for the summer. So that's how I got there.

A (22:03)

You put yourself to school by Tell me about hypercache. You build a piece of software.

B (22:09)

It's the weight loss program for hard drives.

A (22:13)

That was sufficiently useful to a large number of people that would somehow give you money.

B (22:18)

Yeah, it made decent money. I mean, I sold a couple thousand copies at 20 bucks a copy or 40 bucks a copy.

A (22:23)

What program, what language was it written in?

B (22:25)

C. C. So there was some assembler. The actual really tight code to do the real work of transferring data to and from the cache was 68,000 assembly.

A (22:33)

Everything else was C. Okay, this is like file system, IO, device block, IO.

B (22:38)

So any block that gets serviced from the drive would go through my cache first. And it was an N way associative cache. And so it would try to match the geometry of the drive and do prefetch based on, you know, trying to read a whole track at one time, that kind of thing.

A (22:51)

What was it like trying to get your software out there at that time? Like where? How were you able to find customers?

B (22:59)

Yeah, it's interesting. I think I started on Usenet and some of the Amiga forums posted. Here's my trial version. Try it out for 30 days, see what you like. And eventually got picked up by a few retailers. And I remember I was with my now wife in her car and she had a cell phone because her dad was very concerned about her safety. So this is late 80s, and she's got the antenna on the roof and the big box in the trunk, the whole deal. But we got a call from one of the software retail, wanted to buy 50 copies at 20 bucks, which to me is 1,000 bucks, which in 1989 or whatever year it is, was a big deal. And so eventually a number of companies just bought inventory.

A (23:34)

Let's go to that time. It's such an interesting time with Bill Gates and Microsoft. Why do you think Microsoft was dominating the software and the personal computing space at that time and really for many, many, many years after?

B (23:46)

At the time, it was the single most potent assemblage of smart people that I've ever been a part of. And I've been in academia and I've been in industry to a certain extent. And you know that when you're working at a regular computer company, the one guy who actually knows what he's doing, his smarter friend, he probably works at Microsoft. So when you get there, you're the big chiefs from your small town, you think you know a lot, and all of a sudden you're just in an environment where you're like, oh, I'm just not going to speak because I don't want to look stupid.

A (24:14)

Okay, what about Bill Gates himself? What are some qualities of Bill Gates that you think contribute to the success of Microsoft?

B (24:22)

I think he was relentless in the pursuit of his one dream, which was his old slogan of a computer in every home and a computer in every desk. It was his special interest. He was a smart guy, super determined, and he hired people that were as smart or smarter than him to help him execute it. And he built an almost unstoppable machine of intellect to go forth and make, let's say, very simple products. Mississippi. DOS is not a complicated product by any stretch, but it's exactly what the market needed at that time.

A (24:50)

Yeah, I mean, Ms. DOS changed the game. And that's actually the team you joined, the Ms. DOS team, and I think you joined before Windows 95 was released. So tell me about the story of Ms. Dos. Success of Ms. DOS is probably pivotal to the success of Microsoft.

B (25:11)

Yeah, before dos, they were largely a language company, so they had made BASIC for a lot of computers, and they had a FORTRAN compiler and a Pascal compiler, that kind of thing. But their deal to have Ms. DOS included with every version or every instance of the PC effectively set them as a standard that they were able to leverage for decades going forward. And to a certain extent, they lucked into that. And on another hand, they were smart to have done it so because they didn't charge IBM a lot of money for it. But making it a standard really played out to their advantage over time.

A (25:45)

So at that time, Ms. Dos, no graphical interface. Can you just speak to what the heck Ms. DOS is?

B (25:51)

It's largely a command launcher. So you type in a name of a command it looks up to see if that's in the current directory or on a special path of folders, and it loads it into memory and executes it if it's there. And that's 90% of what Ms. DOS does. Now it has environment variables and some complexity and a small scripting language built in. But it is basically just an operating system shell that allows you to use the resources of the computer like the hard drive or the cpu, and it doesn't allow you to multitask. There's no graphical interface. Now Microsoft did add a text based graphical interface for things like an editor and quick basic in DOS 5, I believe. And it was a DOS shell which was sort of a graphical file manager in ms.doS4. So they experimented with it, but it's largely a command prompt.

A (26:35)

Does it have ability to communicate with external devices, so drivers and all that kind of stuff? Like how expansive of an operating system was Ms. DOS?

B (26:45)

Well, it was limited by the original x86 instruction set, which limited it to 640k and then reverse band aids on top of that to do high MEM and then extended memory beyond that. And a lot of hoops have to be jumped through to make anything work without consuming base ram.

A (27:03)

Yeah, I mean, so you programmed on Ms. Dos, what's it like? What are some interesting details there? Like you said, there's the memory constraints of 640 kilobytes.

B (27:14)

Yeah. 640k is the maximum that's ever going to be available. So it's not what's available to you as an operating system developer, because whatever you use is what the user won't get. So if you use 10K needlessly, you're going to. Every machine in the world now has 10k less. So that's kind of a big responsibility.

A (27:29)

Is that a true quote from Bill Gates where he said nobody will ever.

B (27:33)

Need more than 640k? Yeah. No, it's not him.

A (27:35)

Okay.

B (27:36)

It's been attributed to him, but not real.

A (27:37)

Okay, so I mean, what are some interesting aspects of that you were able to do as an intern and when you joined on Ms. DOS and beyond?

B (27:45)

One of the first things I did was to take Smart drive, the disk cache, because I had familiarity with disk caches and to add CD ROM caching to it because I was new. CD ROMs were just coming out. Microsoft Bookshelf was one of the few products you could run for it. And as you can imagine, caching a CD speeds it up by dozens of times if you're smart about it. So it was a big performance win and a nice thing to work on. A bigger part of that was moving a bunch of Smart drive and eventually the double space compression engine up into what's known as high memory. And without rat holing on the technical aspect of it. On the X86 there's something I believe called the A20 line. And I probably have this backwards or I got a 5050 shot at it. But if you've got the A20 line asserted, then your memory pointers wrap at the 1 megabyte mark and if not, they don't. So you continue going up in memory. So you can rewrite memory above by combining your segment and offset registers to a number bigger than 1 meg and you get an extra 64k and you put your code in there and then you just put stubs to jump to it from low memory. And so you can get another 64k out of the machine that way. And we did that for a couple of the products. And that's. I had no idea what hi mem was because I was an Amiga programmer and I'd never written any x86 code before I got there, so.

A (28:55)

So that was like a cool optimization that you got to be a part of.

B (28:58)

Yeah.

A (28:59)

So what about Windows? There was a parallel development of Windows 95 right at that time. Did you get a chance to interact with those folks?

B (29:06)

I actually worked on Windows 95 for about three or four months. I was on the Comm Olay team doing the presentation cache, which is when you insert a, say, a word or an Excel spreadsheet or chart into a Word document. You don't want Excel to have to be loaded to render it every time. So there's a presentation cache of enhanced metafiles and I was working on that. So that shipped in Windows 95. But I moved to the Shell team about six months after getting to Microsoft. And so I worked on NT from there forward.

A (29:32)

Okay, and what's 95? What's NT?

B (29:34)

Windows 95 is an evolution of the original 16bit Windows 3.1, which was the very first popular version of Windows. And it adds 32 bit support and VXD drivers and a bunch of new technology and an entirely new user interface. And it's something that at the time was revolutionary. People lined up at night to wait in line to buy the thing.

A (29:54)

Can you just take us back to that time and describe why 95 was such a big leap from 3.1? So Apple already had a graphical interface. Windows 3.1 had a graphical interface. Why was Windows 95 such a gigantic leap?

B (30:10)

I don't want to make it as basic as the Start menu, but I think it's a big part of it. I know when I first saw it I couldn't quantify what about it was different and awesome. But I realized that I wanted to be a part of it. And that's why I started writing a shell extension which became zip folders at some point. But I was just fascinated by the new shell. And that's why I wound up working on the team that brought that shell over to the nt. And what's Windows today?

A (30:33)

Would you say that's the greatest operating system ever? What's the most impactful operating system ever?

B (30:40)

Windows 95 would be number two for me. I think OS360 is going to be number one.

A (30:44)

Okay, interesting.

B (30:45)

Did you take a machine and write a cool ball program for it in 1962? Jump in your time machine, go to Poughkeepsie and boot up an IBM Z17 mainframe and run it today. And they've been doing it for however many years that is. And it's all on the business side. So we as consumers don't have much access to it. But I think it was probably as influential in the commercial side as Windows 95 was in the home side. And then probably Linux would be number three for me. I put Linux as bigger than Unix, which doesn't work because you can't have one without the other. But the impact of Unix, BSD and so forth is largely in the academic space. It's by programmers for programmers.

A (31:23)

So yeah, Linux created, I mean it was the embodiment of the open source spirit at its largest scale. Right. So it almost created a community and it created a spirit of programming that propagates to this day. That's true, that's true. Like scale matters.

B (31:44)

Yeah. And its penetration on the server side of things now is. I don't know if it's equivalent to what System 360 achieved, but it's almost ubiquitous.

A (31:52)

So yeah, the world, I mean, this is the quiet secret of the universe, is it runs on Linux. Okay, so tell me about the days, your work days. What were they like back then, back in the Ms. DOS Windows 95 days take me through a productive day.

B (32:10)

Well, your day starts coming in and you got to download the address book, which is. Microsoft has between 10 and 15,000 employees at this point. And we're all on Ms. Mail. We're just getting off of the PDP 11 called Miss Piggy, which ran Wizmail and we're running Ms. Mail. But Ms. Mail has a fixed address book that every user must download every morning. And when there's 10,000 people downloading 10,000 people, it gets pretty messy. And I think we're on 10 megabit networking at the time. So your first hour is downloading the address book, which was always frustrating, but you'd use that time to look at the crashes that would have happened overnight from a process we called stress, which is nnt. All the machines that are unused run tests all night long and they try to crash themselves. And if they manage to crash themselves, it will drop into a debugger with a serial cable to another machine and you can connect to that other machine and remotely debug the crashed machine. So you come in and they will have triaged bugs. You know, there was a crash in the start menu, so we'll assign that to Dave. And so you come in and that's your first thing is to connect because you got to get that machine back to the guy that owns it and unlock the machine. So that's your first hour of your day is basically triage for bugs that have come up from stress overnight. And then at that point it's probably back to coding, which unfortunately 80% of the time is fixing bugs. Especially in my career, it was porting code and fixing bugs. I wasn't writing a lot of new code and there were exceptions. I wrote a lot of new code on the side to get it out of my system. From a day, day to day grind of always fixing bugs in other people's code, which is amazing learning experience.

A (33:40)

So you did a lot of the. At Microsoft, you did a lot of the porting of, what is it, Windows 95 code to NT.

B (33:47)

Yeah, we took the entire Windows 95 user interface and we ported it to NT, which meant making it Unicode for one thing. So everything that was 8 bits is now 16 bits. So pointers. It's quite a mess when you switch the code over, as you can imagine.

A (34:00)

Can you give us insights in what is involved in porting?

B (34:05)

It's like breaking into somebody's house and going through all their stuff and seeing the stuff in their drawers that they didn't want you to see. Yeah, you find all the good stuff, the pretty pictures hanging on the wall and you find some disturbing stuff in the nightstand. I saw code that was like 200 some characters wide with, you know, profanity and swears in it. And it eventually got all cleaned up over the years by the time I left. But it was not always the most professional code in the world.

A (34:30)

Right. Because every single piece of code you.

B (34:32)

Have to go through line by line. So you see it all.

A (34:35)

Yeah, yeah. I mean, that's the story of programmers. You think you write a piece of code and you think you'll never be seen by anybody. And sometimes, oftentimes that code is going to be seen by a very large number of people that come after you, including you, five years later, you yourself looking at your own code. Okay, so tell me about Windows nt. That was a giant leap too.

B (35:00)

It was, it was basically a clean sheet design. So they went and they got Dave Cutler from Digital Equipment who had done operating systems for them. VMS and RSX11 he had done. And so he came over after, I believe it was Prism and Mica were some projects at DEC west that got canceled. And so you had a whole team of guys with their project just canceled and basically they took a whole bunch of them and came to Microsoft and I don't know the specific of the deal, but they all showed up. So you had Dave Cutler and Mark Lekowski and all these really smart guys from dec and they did basically a clean sheet, but they also had OS2 as a starting point. But OS2 is of course written in assembly language and NT is going to be written in C. So to what extent they were able to leverage any of that, I don't actually know, but at least they had a system to start with.

A (35:46)

You said that Dave Kotler is the man, the mind behind Windows. Can you explain?

B (35:53)

So Dave Cutler is the architect of the kernel. So he is Linus in the Linux world. It's Dave C in the Windows world.

A (36:00)

Dave C. Okay.

B (36:01)

And it's not that there weren't other people that contributed, of course, huge pieces to it, but I think he's the driving force behind it and always, largely has been. And he's still, I think he's 85 now. He still codes every day. He's a Microsoft fellow. He's as far as I know, still goes into work.

A (36:14)

So can you speak to the genius of that guy? Like, what's, what's interesting about his mind having, having worked with him, having interacted with Dave Culler?

B (36:24)

Well, the dude's wicked smart, but he's also like a farmer. He's like the guy that will follow you around and make sure that stuff gets done and gets done right to make sure that you're not checking any crap into his operating system. And he won't tolerate it. And he's a real taskmaster in that regard. But I think it really paid off because it was a very big paradigm shift for Microsoft developers to be subjected to the Dave Cutler Digital Equipment style of leadership.

A (36:50)

What did you learn from that? About to successful software teams where there's a large number of people collaborating because Microsoft had a lot of brilliant engineers back then and like you said, Dave Cutler, they had to. They had to create completely new systems, many of which we still use today. What have you learned about great software engineering teams from that time?

B (37:15)

Tools are everything. I think for one, people are everything. We'll give that as a granted. But the tool set is a huge factor. If we would have had Git, it would have been immensely easier. We were using diff and manual deltas to do this porting and stuff. So being able to fork a branch of source code would be a luxury that is new to me. So at the time it would have been really handy.

A (37:37)

What were some memorable conversations from that time when you walked over next door?

B (37:43)

Well, one I was not present for was somebody was complaining. A new hire came into the team and was working on what I believe was called Cairo. And Cairo was going to be the next future operating system, was going to be beautiful and have a whole new user Interface newer than Windows 95, and it never materialized. But while they were working on it, one of the guys who was working on Cairo was kind of flaming on the Open NT Dev alias, which is thousands of people, how shitty the NT boot experience was. And the response that came back was an epic flame that I wish I would have saved. And I won't name the guy who wrote it. He knows who he is. It was a work of art, of angry flame mail, kind of like the ones you see Linus send every now and then about Colonel stuff. So it's a very similar sentiment.

A (38:26)

Were there like kind of intellectual debates? Like there's some. Some heated stuff with engineers?

B (38:32)

Yeah, it got contentious. So you've got intellects competing and eventually the technical merits for some people are secondary and it's about besting the other person in that argument. And it's no longer productive at that point half the time. But there was a fair bit of that.

A (38:47)

Yeah, I've seen those kind of debates in like programming language design communities like Guido van Rossum, the leaders of those communities, that can wear them down. Because people get you almost like, forget the mission you're on and start being very nitpicky about the details. I mean, engineering minds get together and you just go to war over the stupidest. Like syntax subtlety.

B (39:13)

Right.

A (39:14)

I shouldn't say stupid, but it's a small syntax subtlety that's for programming language. I'm sure there's internal battles about specific kernel components.

B (39:26)

Yeah, I mean, there was one that I lost that still bugs me to this day. I think I was right. Well, when we were doing the shell, we were porting everything from ANSI to Unicode, so every character that was 8 bits now becomes 16 bits. Now the problem is I'm on a MIPS box because I'm porting it to risc. And you can't have unaligned addresses. But if you take two ID lists, which are basically path components, you take the one for C, take the one for Windows, take the one for system 32, and you add them together. But if you've got an odd number of characters now, you're at an odd address in this thing. And it takes me an immense amount of work to turn on exception handlers, to do unaligned byte access, to pull the string out and copy it manually. It's just a. It's literally like a hundred to a thousand times the amount of work to read a string out of this ID list on a MIPS machine because it's unaligned. So I'm having the argument that even though it's late in the Windows 95, they've already shipped one beta, that we should now just guarantee that ID lists are always an even number of bytes or do some hack to just make sure this never happens. So the code that references them on other hardware can just blaze through it. And it became a shouting match and sort of a personal match, and I lost that one. And I still think that I know today that that code running on Windows is thousands of times slower than it has to be. And nobody cares because it's plenty fast, but it could be a lot faster.

A (40:42)

Yeah, so, I mean, you mentioned MIPS and risc. How deeply did you have to understand the lowest level? So the lowest level of the software and even the hardware with the stuff you were building, like, what are the layers of the abstractions you had to understand to be successful with all the stuff you're doing with NT and before that with Ms. Dos, well, about half.

B (41:06)

Your day is going to be spent debugging. And most of that time is going to be spent in call stacks that are in pure assembly language because there's no source level debugging. So it's not like we're in Visual Studio and you hit a breakpoint and it pops up and there's the source code. You can go look at the source code, but you're looking at the raw assembly dump from the machine at all times.

A (41:23)

Even if you're programming in C, the debugging is in assembly.

B (41:26)

Yeah, a hundred percent.

A (41:28)

Oh, man.

B (41:29)

So it's a little cumbersome. Better yet, we're doing four instruction sets because we're doing Intel, MIPS, Alpha and PowerPC. So depending on which machine it crashes on, you've got an entirely different instruction set, the registers. So you get reasonably adept at debugging all four. But I had more experience in mips, so MIPS stuff would come my way.

A (41:48)

That's a real endurance event. I mean, can you speak to that? The torture. There's debugging, especially that kind of debugging without the tooling associated with it. I mean, that's, you know, programming kids these days, programming isn't all about creating beautiful things. Right. It's also about fixing things.

B (42:12)

Yeah. I would say that 20% of my professional life has been creating and 80% has been debugging and fixing.

A (42:17)

Yeah.

B (42:18)

And I mean, I got a bit of a reputation as somebody who could fix stuff and so stuff like that would flow to me and so I would spend more time doing that. I wasn't renowned as a creative UI genius where I'm flowering all these new ideas, so I got to fix ugly stuff. But you get really good at that. So I don't mind it until it's one of those things where you've been chasing it for so long that you don't know what to do next and you can't understand why it doesn't work or how it ever worked or whatever situation you have to be in. And you know, after a day of it, it can get pretty trying.

A (42:46)

Yeah, debugging can be real torture. It can be really, really difficult. There's a psychological component, I think, of perseverance.

B (42:54)

I think the ones that take you a day, they resolve one of two ways. Either it's like, oh, extra semicolon and then you finally see it, or it's some horrible manifestation of cross threaded apartment nonsense. That was really hard. But it can go both ways. I had a bug. It wasn't my bug actually, but it was a manifestation of A bug in Task Manager where every now and then it would say greater than 100% total CPU usage. And this looks pretty silly for a Task manager. So I had tried to resolve it for a long time and I'd talked to the kernel guys about my issue and they were unsympathetic, let's say, because the kernel guys are a special breed and they weren't interested in my user land problems. It's probably some issue in my code, right? And they're probably right. But it wasn't in this case and I was sure of it. And so I kept adding asserts all through the code to make sure that the preparatory steps of adding the stuff together were never more than 100 and that the final sum was never more than 100. And finally it never asserted. But occasionally we would get this bug where people would still see it. And so I finally put my phone number in the assert and I was like, if you see this message called Davepl at 425836 my phone number. And finally we did get a catch in the actual stress debugger that I was talking about earlier where it happened to somebody with a debugger connected, we were able to go through and it was actually a kernel accounting issue and it wasn't a Task Manager issue. So they just fixed it in the kernel once I was able to prove that it was in fact the kernel issue. And you'd think we would then remove my phone number, but we just commented it out, so it's shipped and it's in all the damn source code leaks for NT that are out there. So that's how I find Task Manager code is I search for my phone number on Google and it will reverse find the NT source code.

A (44:32)

Can you speak to the assert thing? By the way, I saw, I think he tweeted or he said somewhere that if you want to take your assert really seriously, you add your home phone number in there. It's true.

B (44:42)

A little facetious because it's probably not the smartest thing, but you will find out.

A (44:46)

But I mean, assert by itself is already a serious thing because it stops at all execution. This is one of the reasons I really, really love asserts, because they stop everything and force you to take care of the problem.

B (45:01)

Yeah, I'm a little religious about my asserts too. I don't assert things that I hope aren't true. I assert things that I know cannot be true. And I think that's really the intent of an assertion. So I'm overstating the obvious, but when it does occur. It's a bug, plain and simple. It's not a warning.

A (45:15)

It's kind of fascinating how often it can really help you figure out the problem. Because if you put asserts everywhere, you can get very quickly to the source of the problem.

B (45:27)

Yeah, I tend to. It's not something that I want to suggest you go back and add later. It's something you should do organically as you build your code. So for each function, if you've got assumptions like I know that this pointer is never null, well, assert that if you know this count is always less than twice the byte width, assert that. And don't be afraid, because if it asserts, it's doing you a favor. I think some people are afraid. You know, it's like when you turn out of an intersection and you think maybe there's somebody coming and you don't look left, or maybe I want to do that. But it's like that. People don't assert because they're afraid they're going to fire. Well, no, you want to know.

A (45:59)

You mentioned Task Manager. Obviously we have to talk about this. The legendary program that you created, the Windows Task Manager. Tell me every detail of how you built it. What is Windows Task Manager?

B (46:11)

So Windows Task Manager is a way to go in and find out which apps on your system are using the computer, using the hardware, using the cpu, using the memory, and which ones might be using too much or locked up or going crazy. And it gives you the ability to terminate and kill those ones. So it's an inspection and a fixing tool?

A (46:28)

Yeah, it lists all the processes. I mean, it's a legendary piece of software. It's crazy. You just take it for granted. It's like the start menu, right? Yeah, it's like genius.

B (46:37)

Well, I had the great fortune of working on a lot of things that people are familiar with. And Task Manager is one of those side projects that I started as something that I wanted for myself and eventually came in house. So I started writing it at home and I got kind of the basics up and running and I was using, I think it's Hkey current performer, Hkey performance in the registry to get the stats because I didn't have access to the internal APIs because I was working from home. And I don't call those if I'm working from home. And when I brought it in house, then I was able to call things like antiquery system information or antique process information and get the real answers very quickly, which enabled it to become a very fast responsive app. So people have come to rely on it because I wrote it to be as reliable as possible. I wasn't worried about features. There was a basic set of functionality that I wanted in there and I got everything I wanted, but I wanted it to be really robust. And so that. And small. And the original was like 87k.

A (47:28)

Okay, can you speak to what it takes to build a piece of software like that that doesn't freeze?

B (47:34)

You don't assume much. Right. If you're going to call the shell to run an app, well, that could be a network path that's on a TCP IP share that takes 90 seconds to time out. So anytime you do any kind of API call like that, that could take time, you're going to wind up doing it on a separate thread and so the app becomes a little more complex because everything is multi. Threaded.

A (47:52)

Okay, so what programming language were you working in? C. So this was for Windows NT?

B (47:58)

Yes. So this shipped initially in NT4.

A (48:01)

Okay, so what are some interesting details about this program because you have to get it as simple as possible, but also as robust as possible. What are some interesting optimizations, for example, you have to implement.

B (48:13)

There's a couple things that are a little hardcore now. I'm surprised I did. Like, I didn't want to link to the C runtimes at all. So I made sure never to call a runtime call and I didn't link to them. And that saved me whatever The C runtime is.96k or something. So, you know, it almost doubled the size of the app if you just touched any C call. So I was careful not to do that. But then I was actually writing in C, which was C with objects more than anything. But in order to get it to work, I had to go through and call all the object constructors manually from the dispatch table and stuff, because you don't have the runtimes to do it for you. So you're working with a compiler that doesn't have its runtime. And I don't want to rat hole on the technical issues, but it's a lot of extra work to get it to work. But when you do, it's incredibly small and tight.

A (48:53)

That's about the size the program. What are some interesting aspects of tracking down like every. Every process and how much CPU usage?

B (49:03)

One of the cooler things that I saw is, I don't want to say I invented hamming code, but I kind of invented hamming code without knowing hamming code existed. So every column and every row in Task Manager has a bit on whether it's become dirty or not. And then I can look basically the same way. Hamming code looks in your X and Y columns to find out which rows have changed, go through and find out which ones actually need to be repainted. So Task Manager is super efficient, and it works in concert with the ListView control, which provides that functionality to go through and repaint as little as an individual cell that changes from frame to frame. So it could paint very fast. It can resize very smoothly. And resizing was probably my biggest personal goal with that app. So you can size it to any size and it still works. And even if you have 32 CPUs, which wasn't possible in the day, it will draw, I think, only eight graphs and then it wraps, but it still works today. So kind of proud of that.

A (49:59)

It's just incredible. You've gotten the chance to sort of observe the evolution of Task Manager. In some ways. It really hasn't changed much. Maybe there's some prettier aspects to it that fit into the whatever version of Windows it's in, but it's really basically the same thing.

B (50:16)

The functionality is very same. The reporting is more. Because they've added GPU and thermals and things like that, which is really nice to have. We didn't have that ability in the day.

A (50:25)

So, I mean, what can you say? Do you know about, like, was there any refactoring done, or is it basically the same code?

B (50:31)

As far as I know, the original code's still mostly all there, so there are layers of drawing code and dark mode code and whatever else, XML schema code that goes on top of that. That makes it 4 megabytes instead of 87k, but that's the world we live in.

A (50:44)

So, yeah, it's one of those pieces of software you create and just stay once it's there, it's really like the Start menu. And then I'm sure if you remove it, people will just lose their mind.

B (50:56)

Yeah, it might be locked in for a while on that one. It might be good.

A (50:59)

Yeah, I thought that would be true for Clippy, but Clippy will make it back one day. All right. What are some other pieces of software you created at the time that are legendary? So you were part of Space Cadet Pinball, at least porting.

B (51:16)

Yeah. So they came into my office and said, hey, what are you doing? And I said, I told them what I was doing. They said, well, how do you want to spend your next three months? I said, I have no idea. And he said, you want to port Pinball? And I'd seen Spacecraft Pinball as a game standalone for the Win95 platform. And it had a couple different tables and it was a cool game. So I was kind of excited. What they wanted was some visual splash for NT to show that NT can do for then high speed graphics and or at least responsive graphics. And so I took a shot and unfortunately a lot of the code was in assembly and I was on the mips, so I had to rewrite the code in C so I could then port it to all the different platforms. And at the heart of the game is a huge state engine. It's like a giant switch statement with if I remember, like 50 entries in it.

A (51:59)

Yeah.

B (52:00)

And it's got an Easter egg built in and decoding the state. It's like running a neural network through this thing as you hit it with different states. And I just put it aside and treated it as a black box. And so my code runs on top of that and does the drawing and the sound and everything else. But the original game is still running. And somebody recently asked me why is it slightly different. The physics are slightly different from the Windows 95 version, but it should be the same code because I'm trying very hard to preserve that. But what it is is I had a bug where I will draw as many frames per second as I can, which on a modern computer could be 5000 frames a second for Pinball because it's a pretty basic game and so all your physics are interpolated 5,000 times per second instead of 30 times a second or whatever you would have got in the old one. So you're getting arguably better or at least different physics. But they fixed that since.

A (52:50)

So why is that game so awesome?

B (52:52)

I think it's a great design. I mean, I take no credit for that. That's all totally the guys at Cinematronics. But the original game is a great design. It's very similar to Black Knight 2000, which I own as an actual physical pinball mach. And the layout is actually very similar. I don't know if it was inspired by it or not. So it's a good game.

A (53:08)

Yeah. Sometimes I think about like Tetris, about certain games with pretty primitive graphics that captivate the. The excitement of a large number of people. And maybe it's the excitement of a large number of people that contributes to the awesomeness of the game. So when many people together get excited and talk about it, that sort of gets implanted into your head. But that's one of the great games. Even like Solitaire Minesweeper, I Mean, there's just a generation of people that have gone to war in Minesweeper, right?

B (53:41)

Well, those things were included in the OS not as games, but as educational tools to get you to use a mouse.

A (53:46)

Oh, interesting.

B (53:47)

So solitaire is there to show you how to do drag and drop.

A (53:50)

Yeah.

B (53:50)

And Minesweeper is probably right click. I think you put a flag or something. Not a Minesweeper guy. So each one of them teaches you something. Minesweeper guy.

A (53:58)

That's funny. Yeah. Wow, I didn't know that. That's interesting and that's true, but I don't know how many hours I've spent on these games and like millions of people spent millions of hours on these games.

B (54:09)

I used to volunteer teaching computer science at my kids school, you know, for the third graders and stuff. So it's more like logging in than computer science. But the kids, of course all their dads work at Microsoft, so nobody's impressed by anything you do. But one of the kids found out I worked on Pinball and then they were like, whoa, you worked on Pinball? Because they all knew that in those days. Now the kids are probably aged out, they don't know it anymore. But for a brief period.

A (54:33)

You'Re behind the Windows activation.

B (54:35)

You're saying like it's a bad thing.

A (54:40)

Everything's a matter of perspective. So tell the story of that. What's Windows activation? How'd you get involved?

B (54:46)

So they came to me late in the XP ship process. I don't know if the beta had gone out. I don't think the beta had gone out yet. But they had intended to take the Office activation code and then adapt it to Windows and add activation to Windows. But whoever was responsible for doing it had slipped it enough times that it wasn't going to happen. And so I had kind of reputation for being able to fix things quickly. So they came to me and said, can you get this done in time for xp? I don't know, but I'll try. So with the help of the guys that were doing the DRM stuff on the DRM side and the research guys doing the math for the product keys and everything else, we cranked it out in time for xp. And I don't know what it actual impact is for revenue, but I still just imagine it's substantial when you start enforcing license keys.

A (55:28)

I wonder what it is. I don't know because it's also annoying.

B (55:32)

It is, especially if you have the phone activate. And that was just the case that we had to carry with us as an albatross around our neck where you've got to pass data up to the clearinghouse, the backend systems that are going to approve your key. You've got to tell it all your hardware parameters like how much memory and hard drive space and the various things the hardware key is bound to as well as the product key. And you've got encoded in letters and numbers that somebody's willing to read in over a phone. And if you think doing product activation is painful over the phone, could you imagine being the person that worked on the other end of that line? I mean that's just gotta be a mind numbing job to listen to product keys for eight hours a day.

A (56:07)

Yeah. One of the challenges with Windows and it's been a frustration point for me, but I understand from a design perspective it's very difficult is so many different kinds of people use Windows. But it's been frustrating how over time Windows is more and more leaned into the direction of like not the power user I should say. Which is why sort of Linux has always been really wonderful. But from an activation perspective or from any kind of configuration, it's been a source of a lot of frustration.

B (56:43)

One of my more popular episodes of late has been why you can't move the Windows taskbar. I had no idea. But the outrage is palpable amongst people that you just put on the left or top and you can't anymore. And it is an affront to their existence. And I understand it to a certain extent.

A (56:56)

That's one of the main reasons I really just dislike. There's a lot of aspects about Windows 11 I dislike, one of which is like you can't customize things as much about the position of the taskbar, just basic customization. Can we just configure stuff? Because there's going to be a small contingent of power users that are just going to enjoy the hell out of this operating system. If you just give them that option, it costs you nothing. Just give them that freedom.

B (57:21)

Well, it does cost, right? Because the freedom to put the start menu on the left or the top or the right really increases the complexity of the code that renders the start menu and lays out the tabs and does all the things. And now it's a much larger surface for bugs and it's a much larger piece of code to maintain. So you probably need more developers or another developer or some portion of a developer's time. So the question becomes at what point is it still worth it to satisfy the niche needs of a small set of users? And those decisions weren't mine to make, but I could see it from both sides.

A (57:58)

I think just like the people who make movies and insert very nuanced details that only a small number of people will realize they're there, that's going to really pay off. There's a kind of reputation that builds over time that has a very powerful ripple effect that I think it has. Has so many benefits, including for hiring great software engineers. It's like you create this aura of a place that puts love into every detail, that puts. That really takes care of the power users, that takes care of the developers. I think Microsoft has more and more moved in that direction with GitHub and acquiring GitHub and just taking care of the developers. But on the Windows interface side, come on, some customization. With VS code, you can customize everything. Why can't we customize the Start menu? All right. Anyway. And the taskbar and really every aspect of the Windows interface. I don't.

B (59:11)

I don't.

A (59:11)

I. Maybe you're right. Maybe it increases the complexity of the code. I suspect that's just not the case.

B (59:18)

I bet it was. I bet it was a scheduling decision when they rewrote the Start menu. I think they rewrote it because it's different than the old taskbar. And somebody was tasked with, you've got to deliver this set of functionality. And if I cut out putting it on the left and the top and the right and two rows of tabs and all the other cool features, I can deliver it four months sooner. And I'm not saying that's the right decision, but I'm guessing that might be the kind of thing that motivates it. And they're on such a different release schedule now. It used to be you won't see much craftsmanship unless somebody owns a component for a long time and it settles to a point that then you can work on and polish it. Right. But if it's always churning and the UI is changing every release, it's never going to get that level of polish. Although I think the UI is pretty nice.

A (59:59)

But I. Yeah, it is nice, but I think there. I think it's. I just don't think it's a scheduling thing. I think it's a craftsmanship thing. Just like you with it with a task manager. If there's a guy or a girl in there who take ownership of it, who have, like, passionate, like, for them, it's a thing that they take pride in over a period of time. They can, like by themselves in a short amount of time create something Truly wonderful.

B (60:27)

Right.

A (60:27)

And like I, I, I think if you have large software engineering teams with managers and scheduling of meetings and all this kind of stuff. Yeah, okay then, then your argument applies. But if the, if you allow the flourishing of individuals that create cool shit and like their own sort of the side project, which Google is very good.

B (60:48)

They'Ve tried that, right? Google?

A (60:49)

Yeah, yeah. Like have fun with it, like do some crazy stuff and then we'll integrate it, we'll try to integrate into the whole ecosystem. I don't know because to me it's such a great joy from an individual developer to create something like customization of the start menu of the taskbar because you know that millions of people are going to use it the taskbar and then you know that thousands, tens of thousands of developers might be using to customize even little subtle aspects of the taskbar. You know how much joy you create, you give to people to customize to have some kind of JSON thing where you customize something about the taskbar.

B (61:31)

Okay, but how do you respond to the Steve Jobs aspect of giving you customization implies that we couldn't figure out the right answer for you. Or maybe there is no right answer and all four answers are equally right. I have no idea.

A (61:44)

But right. I think I've always, I'm glad Apple exists. It's a beautiful thing and that ideal of design is wonderful. But I always thought that Windows creates the contrast. Like the point of Windows is to be the operating system that works on all kinds of devices that just is supposed to be much more open and they've moved towards that direction more and more with Windows subsystems. For Linux it's just this whole developer friendly ecosystem. The interface should be in the spirit of that, I think.

B (62:15)

Right.

A (62:15)

But I do think that there could also be security vulnerabilities that created with that. It's not just the complexity of the code because Windows is just under attack. Yeah, it's very difficult to keep it secure. Anyway, taking that tangent, you also developed the zip file support for Windows creating visual zip, like I mentioned, zip folders that eventually evolved into zip folders tell the story of that.

B (62:37)

So that was a piece of software that I wrote at home again. And what happened was I was out with my wife and I think it was a Sunday afternoon. We're driving around, this is 1993 and we're living in our apartment and we're just seeing what the housing market is like out there. And there's a guy, he's got this beautiful three bedroom house and a Corvette convertible, 93 red, torch red parked in the driveway, and houses for sale. And it's like 300k, I think. And there's no chance I'm coming up with 300k at that point or even the down payment on that. So I took the flyer and I cut the picture of the house out and I taped it to my monitor. And that was my incentive to just write something at night. Because when I came home, I was doing two things. I was one, expressing a creativity that I couldn't get out at work when I was just fixing bugs and I was trying to make some extra money. And so I wrote a shell extension before I actually went to the shell team. I started it, and that's what led to my interest in going to the shell team based on a MSDN sample or MSJ at the time, MSJ sample that I saw on how to, like, bring up a folder. Well, once I had the very basic bring up a folder template, adding zip file support to it was just incremental all the way. And I released it as a shareware product. I think it was 1995 or $29.95. And I sold whatever, a couple hundreds or thousands of copies. And one day I'm getting ready for work, and I get a call, and it's a lady, and she says, are you Dave Plummer? And I said, yeah. And she said, are you the guy that wrote Vigil Zip? I said, yeah. She said, well, this is Betsy from Microsoft, and we'd like you to come by and come in and talk about an acquisition of it. I said, okay, what building are you in? She's like, what do you mean? I said, well, I'll come by. And I said, well, no, you got to talk to travel, and you got to talk to legal, and this all has to be set up. And I'm like, I don't get it. We both work at the same place. Why can't I just stop by? I don't know if I said that literally, but it was a few minutes of back and forth where we both realized that she didn't know I worked there. They just cold called the author and then found out that it was me. Yeah, that's funny. So they made me an offer on it. And it's the kind of thing where if I don't accept the offer now, my choices are I can keep selling my own version and quit Microsoft or I can stop selling my own version and work for Microsoft. Neither of those is great. I mean, I keep my job, of course, but I'D like to still have this income stream. And the other option was accept their offer, which is what I did. So then I bought a used 93 red Corvette.

A (64:51)

And you got to continue building it internally.

B (64:54)

I did. So we took a lot of features out.

A (64:56)

Right.

B (64:56)

To simplify it because it had encryption. It had a number of features that were common in zip programs of the day, but probably weren't appropriate for Windows. And at the time encryption was like a munition. So you couldn't just add encryption willy nilly to various parts of the operating system. So we took out some things like that. Multi volume support I think was taken out just to simplify it.

A (65:17)

Well, can you speak to zip in general? Just the history of zip and you know, compression, that whole thing?

B (65:23)

Yeah, it was really born out of the BBS era when people were dialing in on modems to download trialware and shareware and other things from BBS's online and to compress them. Executables compressed about half their size. Other stuff compresses much more. But a guy named Phil Kass came up with a command line program for Ms. DOS called pkzip, which was able to do compression of programs. And he has a rather tragic arc. But it became ubiquitous in the entire PC industry and pretty much everybody was using it. So when Windows came out, there was no way to open up a zip file, but everybody had been creating them for a decade. And so that really drove the desire to have the zip support right into Windows.

A (66:04)

Yeah, and that's another piece of software that just kind of with us to this day.

B (66:09)

And it could be vastly improved. But you know, it was written in a single core day, so it doesn't do anything multi threaded. And you've got a 96 core 7995. Well, it uses one of them to unzip your file.

A (66:19)

What other awesome things were you a part of at Microsoft? What other pieces of software?

B (66:25)

I worked on the initial prototypes of Windows Media center. So we did that in 96 I believe. And we didn't have at the time any sources. So we had like a CD of MPEG video files of Raging Rudolph and I think the original south park video, the Christmas one, which is all wildly inappropriate in the workplace today, but it's all the content we had until we got. Actually we had them put a satellite dish on the roof, a DSS, whatever the 18 Inc. Dishes, because we couldn't get cable to the building. And so we built up this thing that would eventually look a lot like Media center and it was distance viewing UI for Windows. So you could sit with a remote control on a desktop and have you know, the current start menu is not great at 20ft away.

A (67:06)

So tell me the story of the infamous blue screen of death.

B (67:10)

What it is, is when Windows has no other option, when the kernel gets into a state where something illegal has happened. So let's say a device driver is trying to write to a piece of memory he doesn't know, or it's trying to free a memory piece of memory twice, something that just cannot happen. And the kernel has no other option. It will shut the machine down to save your work and, well, not save it, prevent further damage. And it puts up a blue screen and it prints out the stack information. Depending how your settings are, sometimes it's just a sad face in the current Windows.

A (67:40)

Yeah, I wonder what the first version of Windows when the blue screen came to be.

B (67:45)

So Windows 3 had a blue screen, but it's completely unrelated to the blue screen and Windows nt. And I talked to the guy that wrote the blue screen and Windows nt, his name's John Vert. And the reason he picked white on blue, I had thought I'd always heard because in the labs you could walk through a lab where we have 50 PCs all running stress, oh, that one's got a blue screen. It's crashed. It wasn't that simple. It was just the MIPS firmware that he was building it on was blue on white and visual slick edit that he was using. His editor was also the same color scheme. And so you could code, boot, crash and reboot all in the same color scheme.

A (68:19)

Why do you think so many problems with computers can be solved by turning it off and turning it on back again?

B (68:27)

I think there's two major things that happen with computers as you run them over time. One is memory gets used and not freed. And so it accumulates on the heap or in the swap file or wherever, and things get sluggish. And the other is code gets into a state that the developers didn't anticipate or didn't test very well. And maybe that's a rare state, but now that Notepad or Word or Excel is in that state, your system is goofy. So if you just reboot the thing or shut it down or restart it, you're getting a fresh state and there's no memory leaks. So it covers a lot of sins, basically.

A (68:57)

And the intricate ways that several pieces of software in a goofy state interact with each other creates sort of a meta goofy state that just kind of just the entire System starts acting a little weird.

B (69:12)

Yeah.

A (69:12)

And somehow fixes it. What's some of the best and the worst code you've seen during that time? Microsoft. What's some beautiful code and what's some ugly code that pops to memory?

B (69:25)

In terms of beautiful code, there's two that stand out for me. One is the kernel in general. When you get down into the Windows kernel, in the actual NT APIs and stuff, it's very well written and it's written to a standard that you don't see on the user side, or at least is uncommon on the user side. On the user side, probably the coolest code I remember seeing was a guy named Bob Day wrote a named Pipe implementation to eliminate the use of shared memory. So Windows 95 had a big shared segment amongst all the shell processes where it would store stuff that was common to all the shells. We didn't want to do that. Shared memory is a bad idea on NT and an industrial level. So he came up with a way to do it with named pipes. And I remember doing the code review on it and it was very impressive to walk through the code. It was one of those things where it was like, oh, I don't think I could have done that if I was trying.

A (70:13)

Who's the greatest programmer you've ever encountered?

B (70:16)

You know what? I don't think there is anyone. I've met a number of great programmers, but I'll tell you one story that impressed me a lot was when I was brand new at the company, I'd been there like six weeks, and I'm working on this Olay presentation cache that I mentioned earlier, and I'm on Windows 95 and I've got Excel inserted into Word and I'm in the kernel debugger and something's going wrong in the scheduler. And I've been there, you know, I've barely written any x86 code. And I'm looking at the Windows scheduler, trying to figure out why my thing is deadlocked, and eventually I get stuck. So I'm kind of out of my element and I send an email to the Windows 95 kernel team and say, could you send somebody by? And so about 10 minutes later, this developer strolls in and they're just holding a null modem cable, which is to connect my two machines together so they can debug one with the other in case I didn't have it, but it was already set up. And so they sit down and they're using Windebug, which is a horrible debugger. It's just. It's accursed. But they're very, very competent with it. And they are just blasting through the call stacks and they're checking all these objects in the kernel and trying to find out who's waiting on what and why things are deadlocked and what things are signaled and what's not. And it's just this quicksilver ballet of call stacks flying by. And I'm watching this and I'm pretty blown away because I'm a good programmer, but this person is an amazing debugger. And I've never seen a performance like this. And about five minutes in I just hear, oh, I see. And then they disconnected and got up and left. And that was Laura Butler, who became a distinguished engineer at Microsoft. I think she may still be. I'm not sure if she's retired or not, but so she kind of set my template for, you know, what Microsoft developers were like when they were debugging and what kernel developers were like, and even what female developers were like, because I had such a small sample set, but it was a very high standard.

A (71:55)

So there's a few things I love in life more than people who are ultra competent at anything really. But the lower level, the better in the engineering space. They're able to, for example, like run or maintain the infrastructure, the computer infrastructure. So not the individual computer, but the computers communicating together and working together. Those people are just magicians, right? It's so inspiring to make. It's like watching a great, like carpenter or.

B (72:22)

I love anything done really, really well.

A (72:24)

Yeah, it's beautiful to see. It's beautiful to see that humans are able to accomplish that, even in civil engineering space. When I look at like bridges, it's like the number of people that had to come together to build that and now millions of people use it every single day. With software, sometimes you don't get to see visually just the number of people impacted by a thing. So imagine how many people are impacted by Linux and all the different open source systems that make up Linux. It's incredible. And Task Manager is an example of a piece of software. Just how many people use that over the years, how many times. It's crazy. It's probably billions. Billions of users.

B (73:06)

Yeah, 2 billion a month or something. 2 billion, something like that. I've seen the metrics and it's up there.

A (73:11)

Crazy to you.

B (73:12)

It is what I love about it though. And I'm sure you've had this experience where sometimes you design a piece of software and it's complex and you get it working in your head and you get the plumbing working and you know how it's going to run and flow. And then eventually you write the code and the code does that thing that you had pictured in your head, and now there are billions of copies of that thing that I had in my head running on millions of people or billions of people's machines. And that in itself is really cool to me. It's not a vanity thing so much as a. I'm impressed by it, I guess.

A (73:40)

How's your programming evolved over the years?

B (73:44)

I take a lot more care and complexity these days. So it used to be you would write code and just keep writing code and writing code, and then at some point I go back and clean it up. Well, I write the other way now. I try to write really clean initial skeletal code and then flesh it out. Because I have been involved in too many projects of my own and of other people's makings where things get so messed up that they're just not fixable. And so sometimes the work you put in upfront pays off.

A (74:11)

You know, what programming languages have you used over the years? What's been your main go to?

B (74:16)

For me, it's been C and assembly language.

A (74:19)

And still to this day, C is really what you lean on.

B (74:22)

Yeah, right now I'm 100% Lua and Python, but that's just side project I'm working on.

A (74:27)

Can you speak to the Lua and the Python detour that you took? And what do you love about C?

B (74:34)

What I'm doing is I wanted to build an AI to play the game Tempest. That's the old Atari game Tempest. And this is a game that I actually hold the world record on.

A (74:42)

And you take me to this Atari game Tempest. Okay, Atari Tempest. What kind of game is this?

B (74:49)

So it's a 3D vector game from 1980. And it's a very complex game. You got full 360 degrees of motion. You have eight shots on the screen. There's like 11 enemies, there's spikes. So it's a very complex game. It's not like trying to, you know, do Pong or something.

A (75:03)

Okay.

B (75:04)

And what I wound up doing was first taking the roms out of the machine and reverse engineering the code. So I got a sense of where all the code in Tempest lives and what it does. Where the zero page variables are where things live. Yeah, there's one.

A (75:17)

So what? Oh, wow. That's a very geometric. Okay, what can you explain to me the gameplay?

B (75:22)

I'm playing the game right there.

A (75:23)

This is literally you playing?

B (75:25)

This is me, Dave, is the high score. You'll see in the top center.

A (75:28)

Can you explain to me what I'm looking at?

B (75:30)

Well, it's a 3D geometric world. It's basically 3D Space Invaders wrapped into a shape, and the enemies descend from the center of the tube towards the outside, and they all have different behaviors.

A (75:43)

Wow.

B (75:44)

So, long story short, it's a fairly complicated game to play well, and I wanted to see if I could get an AI to do it. And so once I had figured out where all the interesting parts of the game lived in memory, I added them as parameters and built a LUA app to extract everything from the game's memory as it's running and put them together as parameters, which sends it to the python side over a socket, and then the python side does RL learning. I'm using a dueling deep Q, and I believe with two head and a tail, and they chase each other. And it can play up to about level 36 now, which is way better than most humans, but that's level 96, so it's got a ways to go yet, but.

A (76:21)

And you're the red thing shooting. You can controlling the right thing. That's shooting. Okay, what are the options? You can just move clockwise or counterclockwise, and then you can shoot.

B (76:31)

Yeah. So you have a rotating knob, which is an optical spinner, and you have a fire button and a super zapper for emergencies, but that's it. Fire and rotate, basically.

A (76:40)

All right, let's get back to your favorite C. What do you love about C? Why have you stayed with it for all these years?

B (76:45)

Because it allows me to encapsulate my favorite C code in classes. I'm not a big. Well, I actually.

A (76:51)

You're really a C guy. Okay, I got you.

B (76:53)

Yeah, I'm really a C guy. Although I write two kinds of C. I Write really modern C20 using no pointers, no string, or no character strings. So they're, you know, it's basically as safe as Rust, as far as I'm concerned. Or I write C with classes, which is standard C, but, you know, with polymorphism encapsulation. And that's most of what my code is, but I try to do both.

A (77:17)

Let me ask you about the whole stretch of time that we kind of skipped over. You built a lot of software over the years after Microsoft, on the side, while at Microsoft and afterwards, a lot of successful pieces of software. One of your companies was software online, and it got into trouble for nagging users. Too much, I guess. To upgrade. That's what I saw. What was all that about? And what did you learn from that.

B (77:42)

Experience now that was other than, like family health scares, you know, when kids are sick. That was the scariest time of my life. And the period leading up to it was one of the most invigorating and exciting because what had happened was while I was at Microsoft, I had written all these shareware utilities and I was selling them on the side and sold one to Microsoft as we talked about, and they started to do really well. And then I discovered banner advertising online. And so I signed up with my credit card for a site, I think it was called Fast Click. And you could say, I will pay this much for a banner ad impression. Here's my banner. And it would rotate it in, and I didn't set a cap on it. I came back on Monday and I saw I had spent like $10,000 in banner ads. I was like, holy crap, how am I going to explain this to my wife? This is a bug. It's a mistake. It was my fault. And I looked at the sales and it had made like $38,000 worth of sales. And I was like, holy cow. So all I have to do is scale that at some point and basically did that for the next several years. And the reason we got in trouble was the AG came in and they had. Well, I was blown away because they had like 12 court claims of action. And 10 of them were outrageous, which to me, as a person with autism, I couldn't get past. It's like, I know these 10 things are absolutely not true. Why are we even here talking about them? And then all they care is the two things that might be true. And the two things that might be true were that it was a 30 day trial version. And after your 30 days were up, it would then, if you continued to run it and not buy it or uninstall it, it would remind you once a day. Not like every 10 minutes, but once a day or every time you booted your computer. At most once a day. And the AG contended that was too often, it amounted to spam. And so we agreed with them to limit it to once a week, I believe. And, you know, there had to be a button to just uninstall with one click. So we did those kinds of things. The other one was in those days, when somebody bought a piece of software, even if they bought it online and got a download, they fully expected they would be media showing up at their house. So in the year 2001, which were 2001, 2003. We're talking about if you bought software, there was an expectation that a disk would show up. And so we made that. The default was to fulfill by disk and it was 3.95 or 4.95 extra. And it was very obvious, but it was a checkbox and it was turned on to ship the disk to your house. Because we found if we didn't do that, we got all these calls. People would wait, they'd order two weeks later call, where's my disk? And we luckily didn't order a disc. Well, cancel it all. I don't want it because I'm not waiting for it. And so we got a lot of returns and we didn't include the disc. And so we decided to include the disc. But that is a priori violation of negative affirmation billing in Washington State because you're giving them a default higher purchase price.

A (80:12)

What about on the software user relationship? It's interesting like how often to annoy the user with the thing. Right. If you never mention anything, they might never discover like something they actually want.

B (80:34)

Right.

A (80:34)

But if you mention it too much then they can get annoyed.

B (80:40)

Yeah. And what you don't want is you don't want them to have to do it or buy it or do something to get rid of it.

A (80:45)

That's one of the things that bothers me with. I think Windows does that a little bit still to this day where it bothers me by asking me certain questions like, do you want this? Like it, for example, I really don't like to use my Microsoft account to log into Windows.

B (81:03)

Right.

A (81:04)

I think now it's like basically required. I think there's just no way around it. But like they make it so difficult to not do that. It's almost like, like they think they could just trick me into. It really does feel like I'm getting tricked into not doing what I want to do.

B (81:26)

Right.

A (81:26)

Like it's. I have to like think, okay, I need to click skip and then it'll do something. Are you sure? Like I have to like use too much of my brain to do the thing I like, you know, as a, as an interface, you know what I'm trying to do? You're trying to trick me into not doing the thing I want to do. And what I hate about that is like it's probably effective, sure. For converting people, but it's really not good long term for taking care of the interest of the user.

B (82:00)

Yeah. The one that really throws me is the use recommended settings. So I just Did Windows upgrade it went through the steps and I'm going through this new dialog or wizard and use recommended settings sounds like the thing you should do. But I'm pretty sure that resets you to using the Edge browser and all this other stuff. So yeah, recommended by them but not recommended for me. And that's the difficulty.

A (82:18)

That's a really good example. Like what effect do you think that does in resetting the default browser to Edge? Do you think you're going to really earn the loyalty of a user if you do that? Don't. Don't you think that they're actually what you're going to create? You're going to create some passive loyalty from some user base. So on the metrics it might actually look like you've increased the number of Edge users, but really it's that reputation hit. You take over time where it just forms where the edge is. The thing that you can't quite trust unfairly because I think Edge is a really great browser. But just this unpleasant feeling, I don't know what that is.

B (83:03)

Well, you don't want your operating system to be an adversary, right? And sometimes Windows can feel adversarial, like it doesn't have your best interests at heart. And that bugs me to a certain extent.

A (83:13)

I mean we have this feeling. I think we just have general distrust when somebody is super nice to you and is basically selling something. There's a certain aura about that kind of interaction. And when an operating system is interacting you with you in that way it's.

B (83:28)

Like yeah, I would much rather pay 199 for Windows Pro per year or 20 bucks a month or whatever the fee schedule would be and not be upsold any further and not have my data monetized and those kinds of things.

A (83:40)

So did you learn about finding the right balance from that?

B (83:44)

Yeah, I mean I'm way more self aware now. There's things I would do much differently, particularly in terms of the advertising. I always figured there's a guy named David Ogilvy and he did this ad long ago for the Volkswagen Beetle where it had a picture of a beetle black and white and it just said lemme and there was a block of text below it. So it's clickbaity and then informational. And I always tried to follow that pattern. But there's three ways to sell something I think. And you can use sex, fear or greed. And sex doesn't work very well for software. Fear works well for antivirus and stuff, but not so much for optimization. And make your computer Faster utilities. And so I always tried to cater to the greed aspect. You know, make your computer faster, get more RAM available, whatever the value proposition is. But I realize now that I'm looking at that with my knowledge and as an autistic person, I now have an appreciation that other people are going to look at it with their background knowledge and may conclude something different. So I might be scaring people where I was just trying to incentivize or get their greed instinct going. So I'd be more sensitive about that kind of thing today.

A (84:44)

Ridiculous question, but what do you think is the top three Windows operating systems, the different versions?

B (84:52)

I'm a fan of Windows 2000 server. That's.

A (84:54)

Wait, what? Really?

B (84:56)

Yeah.

A (84:57)

Okay.

B (84:57)

That's what I ran my business on and I ran my brother's business. We set up multiple salons, all VPN to one another and using the SQL Server.

A (85:04)

And I don't know if I've ever gotten to experience Windows 2000 server. So when was XP out?

B (85:10)

2001?

A (85:11)

What was before XP?

B (85:13)

2000?

A (85:14)

2000. Was that good?

B (85:16)

Yeah, I liked it. I mean, it doesn't have the visual flash that came with xp, but as a system and especially as a server operating system, it was great for the day.

A (85:23)

But then XP was, I would say, probably from a completeness perspective, an impact and how long it lasted. And it's probably the greatest Windows for consumers, the operating system.

B (85:38)

I would think so. It's certainly got the longevity for it. There's people who would still run it. I mean, I'd still run it on stuff if you get security updates, because it does 98% of what I need Windows to do.

A (85:45)

But yeah, that was incredible. So Windows 95. I'll probably put Windows XP as number one for me, and then Windows 95 too.

B (85:54)

What's your metric? Personal preference or industry impact or industry impact?

A (86:00)

Stability. Just. There's certain, like. Just like with programming, you have code smell, just like how well all the features were orchestrated together, how there's a design philosophy that permeated the whole thing and was consistent. Not too many features, not dumbed down too much, but not overcomplicated, how often it crashes, the blue screen, all those things.

B (86:27)

I don't know if it's a very apt description, but I think of it as crisp, so there's not a lot of rough edges. It does what it does.

A (86:32)

It does.

B (86:32)

It's snappy.

A (86:33)

And yeah, you said you play slot machines, and given that you love hardware and software, you're the perfect person to ask, how do slot machines Work well.

B (86:44)

I'm happy to ruin them for you. Okay, so it's ironic to me that I play slot machines because I know it's a losing bet overall, but there's a whole dopamine feast there of bright lights and high contrast colors that I enjoy. So I do play them. But what happens is internally there's basically a black box mechanism that does nothing more than generate the next random number and what the outcome is in terms of probability and payout. And then the game says I got to make up a movie to go along with that. And maybe it's three bars or whatever it is, but there's no correlation. It's not spinning the reels, seeing where they land and looking that up to see what you want. It's completely the other direction. It determines whether or not or if you won. And then make something up to fit.

A (87:22)

That scenario that, that indeed is ruining it for everybody a little bit. What kind of code runs them?

B (87:29)

I don't really know. I tried to get down and get inside access to one and it was very hard. They don't want to tell you a lot about them. I'm sure it's not that deep of a secret, but. Yeah, because they're all basic Windows PCs, but they're basic Windows PCs on top of have a very secure enclave of some kind that I don't know a lot about.

A (87:47)

Yeah, it has to be extremely secure, right?

B (87:49)

Yeah. Well, in the 70s or 80s there was a tech in Vegas went around and he was burning his own ROMs for the slot machines and with a back door in them. And so when he serviced the machine, he would just put his ROM in and he'd come back six months later and nice. Invoke the back door.

A (88:03)

I love humans so much. Anyway. Do you have other, other favorite kinds of systems like that?

B (88:08)

I like a lot of old hardware. I. I restore cars, so I do a lot of 1960s muscle cars, cars and trucks and old computers. So I restore PDP 11s. Has been my fascination and my special interest for the last six months or so. And I've built a number of those.

A (88:24)

Yeah, I've seen like you posting videos about it, the PDP 1183. What's that whole project?

B (88:34)

So basically what it is is I had built a number of PDP 11s and so over the years I had acquired all these parts and I decided, well, let me build the best PDP 11 that I can. And so it was kind of a quest to just like you try to max out a PC. I try to max out a PDP 11. So it's got four megabytes of memory, which would be massive in the day. And. Yeah, that's it there. And it's got lots of blinking lights. And I had to rewrite the BSD kernel to make the lights work.

A (88:59)

And what are we looking at here? What is. What's.

B (89:03)

So the very top is a PDP 1170 control panel, which we can largely ignore. And then there's two chassis below. That one has.

A (89:09)

What are the different knobs? Sorry to ask dumb questions here.

B (89:12)

The knobs control what view you get of the LEDs. So, normally you see the data bus, and you can see the address bus, and you can pause the machine, you can edit the address on the bus, and you can deposit stuff into memory.

A (89:24)

With the switches, man, the haptic, plus the LEDs. That's what you imagine a computer to be. That's so cool. That's so cool. These are. What. What are these? These are DU1. DU2.

B (89:39)

Yeah, it's a weird floppy drive. It's a dual floppy drive with one stepper motor. So both heads seek together like Siamese twins.

A (89:46)

Okay, so what kind of stuff are you doing with this? What are you. Are you trying to restore them?

B (89:50)

Yeah, so I restore them.

A (89:51)

And does it actually run?

B (89:52)

Yeah.

A (89:54)

Are the blinking lights are real?

B (89:55)

Yeah, it's all real.

A (89:57)

Wow.

B (89:58)

Then I had to rebuild the kernel and all that, so I had to learn the BSD kernel. I'm pretty familiar with it now, because you can't just add a device driver, Right? You've got to rebuild the kernel to add support for whatever device. So you add a new disk controller. It's time to build the kernel. So you got to go find the source and find the code.

A (90:14)

You can run code on this?

B (90:15)

Yeah.

A (90:17)

You've written a couple of books on autism. Being autistic yourself, I was wondering if you could tell me about fundamental differences about the mind of a person with autism versus, let's say, a neurotypical individual.

B (90:28)

Well, the fundamental theory of thought for autism is called monotropism. And basically what that means is that my brain does one thing. It does it very intensely, and then when it's done, I can move on and do something else. But I'm not a multitasker. I'm a serial single tasker. By any stretch. Autism usually brings with it sensory sensitivities and repetitive behaviors, behavioral issues that compound it. And if they rise to the level where an individual can't moderate or accommodate them in their life, it becomes a disorder. And that's probably 1 to 2% of the population.

A (91:01)

What's the biggest benefit of life with autism?

B (91:05)

I can bring to bear an incredible amount of focus and dedication on a particular task. And it has to be something I love. It has to be something that's rewarding. It has to be something I can make progress on. And there has to be all these things that are true about it. And it could be like a kid playing with trains. I get that same feeling.

A (91:22)

That said, you also said that you struggle with adhd.

B (91:26)

Yeah, a fair bit.

A (91:27)

So that's part of the component, like.

B (91:30)

Maintaining the focus or actually acquiring the focus is the issue. So I'm very easily distracted. I fall asleep with noise canceling headphones, or I can't fall asleep, that kind of thing. But once I get locked in, I'm very hard to distract. So it's kind of a paradox.

A (91:46)

Oh, that's fascinating.

B (91:47)

It's hard to get into that state.

A (91:48)

Okay, what's the biggest challenge of life with an autistic mind?

B (91:51)

That I don't know what anybody else is thinking. So I know what I would think about this interaction if I was in your position and I was you, and that's the best I can do. But I think most neurotypical people have a sense of, well, Lex probably feels this way or that way because he's acting this way. And his reactions are this and his facial expressions say this. And that's all kind of lost on me. So I run a little proxy NPC game for everybody I deal with.

A (92:13)

So I guess that makes social interaction a little bit complicated.

B (92:16)

It can be, yeah. Telephone is especially hard because I rely on a lot of other cues. And when somebody is just on the phone and I just have their voice, there's so much that's implied between people that I miss. And so I'm much better on FaceTime where if somebody makes a joke, they might smile. After we're on the phone, I don't know if you're being sarcastic or serious and that kind of thing.

A (92:36)

So that's probably gotten you into trouble over the years. A bit, yeah.

B (92:40)

There's lots of times with my wife too, where. Well, there's a certain literalism that comes with autism. And we spent years where she would say something and I'd say, but that doesn't make sense. You know what I mean? I'm like, no, I know what you said. And I'm not being just combative here. I literally only know what you said, and I don't have that. And I remember we've been in meetings with people, and there's three or four people in the meeting. And I'm the only autistic person. I'll tell that they've got this communication loop going on. And I feel like you got to tell me what's going on, because I really don't know what's being said here.

A (93:13)

You told me, related to this, that there was an early, somewhat awkward encounter with Bill Gates. Can you share the. The story of that interaction and how autism comes into play here?

B (93:26)

Yeah. My very first summer at Microsoft, when I got the internship, Bill had all the interns over. I GUESS it was 20 or maybe 25 of us that got hired that year over to his house for burgers and beers and just chat in the backyard. And of course, it's still Bill Gates. And he's a big enough deal even then that you're a little nervous. And so my manager, Ben, who was sort of my mentor at the time, took me over to introduce me to Bill because he knew him, and he's explaining. This is Dave. He's our intern from Canada. And in the space of four months, he's done this feature in just copy and smart driving, listed off all the stuff I was doing. But I stopped because I'm like, well, actually, it was three months. I had to interrupt them, and they both kind of. What? And I looked at each other and I realized that was the wrong time to correct the guy.

A (94:10)

But, yeah, so they both like little inaccuracies.

B (94:13)

Oh, drive me crazy.

A (94:14)

Crazy, yeah. And then, of course, you don't. The. The impact that might have on a. On a casual social interaction. It's. It's not trivial for you to be aware of that.

B (94:31)

Yeah, I'm much better than I used to be before. I didn't know. And I didn't know how injecting a correction meaninglessly into a conversation could impact. To make the other person feel. Now I got a better sense of it.

A (94:42)

But what advice would you have for folks who have an autistic mind on how to flourish in this world in.

B (94:50)

Terms of prosperity and finances? The biggest thing I can say is sell what you can do and not yourself. Because if you go into a job interview and you try to wow them with your personality and how amazing you are, it may or may not go well. But if you can go in with your portfolio of work and say, look, here's my GitHub history, and here are the awesome projects I contributed to, and here's the actual algorithm I wrote, and this is what I do. I Think you get a lot further with that. So whether you're playing the piano or writing code.

A (95:15)

That said, so much of software engineering on large teams has a social component to it, right?

B (95:23)

It does. And that was a liability for me.

A (95:25)

How do you. How do you. I mean, what have you learned about how to solve that little puzzle?

B (95:29)

I think the biggest deficit for me was when I started to manage people, because now you're concerned about their hopes, dreams, aspirations, what motivates them. They have entire lives that are kind of a mystery to me because I assume they want to be motivated and led and encouraged and compensated exactly as I would. And that's not always the case. Some people need a lot more affirmation. Some people just want money. Some people want to be in the important meetings and make decisions, but I was largely oblivious to that. And so eventually I had to learn that everybody that you're managing has their own set of incentives and priorities, and they're completely different from what I think they probably are.

A (96:05)

So you could, I guess, make things more explicit and just. Just communicate better. But, like, ask them about what their interests are.

B (96:12)

And that's something I started doing, is overtly asking because it's hard for me to nudge somebody there. I'm not good with that kind of social dance. So.

A (96:21)

Yeah, part of the social dance is there's a lot of stuff that's unsaid you can kind of figure out you can read people, but if that's, you know, with autism, it might be a little bit difficult to do that. And so you have to make things more explicit. Plus, like sarcasm and satire and humor might be difficult. Yeah, I would love to be a fly in the wall. Some of your earlier interactions with Microsoft. I mean, some of the greatest engineers have in mind like this.

B (96:51)

So, yeah, I've had laptops thrown at me and stuff, and I'm sure it was my own fault.

A (96:55)

You write about the 10 second autism test. Could you explain how this works?

B (96:59)

Yeah. Now, of course, anything that has two answers has a high error rate, but so what's more important to society as a whole from the people, is it cooperation or creativity? And if you had to pick one, which is the most important and most neurotypical? People will generally lean towards cooperation, whereas people on the spectrum tend to lean towards creativity. As individual problem solvers, of course, there's.

A (97:20)

Some kind of error right there.

B (97:22)

So if you want to double your precision, you can use the second test, which is you ask. There's a room with 10 chairs and six people come in and sit down in those chairs. How many chairs are left? Now, some people are going to say four, but I'm going to say 10, because that's how many chairs are still there, literally. True. And I'm not being a dick, I'm not trying to be complicated, but that is how my mind works. And so when I see that question, it's like how you answer it.

A (97:46)

So you're how literally you take things.

B (97:51)

Yeah, everything is very literal for me. I remember as a kid, my grandfather was building a. A planter holder in the kitchen for my mom. And he was using these big angle brackets that I thought were a little overkill. And I said, do you think that'll be big enough to hold the plant? And he says it'll be big enough to hold a horse. And I was only five, but I was very confused about a why you would bring a horse into your kitchen, why you would put a horse up on a plant there. And all of these things that didn't make any sense to me when obviously it was a figure of speech. But for a lot of my life I took figures of speech as literal.

A (98:20)

You mentioned emotional post processing as a strategy you use to replace social interactions so you can sort of reverse engineer to help you understand the neurotypical world. I think this is going to be useful to a lot of people. Like, what does that entail? How does that help you?

B (98:37)

So if I meet somebody, particularly somebody new, and it's my first couple interactions with them, it's like even meeting you today, then I will go home later and replay all of the moments where I had choices to make and probably the most uncomfortable ones. First. First to find out what did I do wrong in that moment? What did I miss? What was the other person thinking? How can I improve that kind of situation next time? And do I need to go fix it or make a phone call, that kind of thing in a bad extreme case, and that's happened a couple times in my life. I had a car restored that my dad had bought new in 69. I still have it. So we've had it 50 years. And about 20 years ago I had it restored. And it was a three year process of craftsmen working on this car for thousands of hours. Hours. And I go out to pick it up and I'm inspecting the car and I'm very impressed with the work. And I'm saying, oh, this is nice and this is great and everything else. And then I fly home and write the check and the car gets delivered. And then I realized probably 10 years later that I had a whole bunch of craftsmen that had worked on my car for three years and I probably should have blown some smoke up their butts, but what a great job they did. But I never did that because it's not what I wanted or needed in that moment. And I was completely oblivious to that. So I sent an email to the manager or to the owner of the place and I said, I don't know if you remember this, but 10 years ago I picked up my car and I probably looked unimpressed, but I want you to know that I was very impressed with everything and the quality, everything else. And he wrote back, he's like, I've thought of that moment often. So I'm like, now I'm glad about it. Up.

A (100:02)

There's subtle things about human interaction that mean a lot to people. And if you ask them straight up, they might not be able to sort of articulate that, but it means a lot. And when it's off, when something is off, it bothers them.

B (100:15)

Right.

A (100:16)

But to reverse engineer that, to figure that out for a person who might not sense those little subtleties of human interaction is tough.

B (100:26)

That's a good point to jump in there too, on empathy, because there is some perception in the community that people with autism lack empathy. And I don't think that's the case at all. I can only speak for myself. I feel fairly empathetic. But I think the problem is a communication one, and it works in both directions. Whereas I don't know how you're feeling. So it's hard for me to be empathetic with it until you communicate to me what it is you're experiencing. And then once I know, once I have an understanding of what's going on in your head, I can feel incredibly sorry for you. But until then, I'm going to assume you're going to handle it just like I would in your position. In my case, with what I know.

A (100:59)

Now, what advice would you give to people, like, on the other side? How they can help you be a better friend or better partner, better colleague? Like how they should communicate with you to help give more information?

B (101:12)

Yeah. Be really specific and don't assume I'm going to pick up on clues and nuance and subtlety. So if you're trying to nudge me into a particular behavior, you're much better off. Say, Dave, this is what you need to do.

A (101:24)

Have I failed in any way today?

B (101:26)

No, not yet.

A (101:27)

All right, what score would you give me? 1 to 10? - 6? 7. Communication 7. 5. Floating point. Nice masking you got to tell me what that is. It's a significant experience for many on the spectrum. What is masking. And tell me about any of the experiences you've had with masking.

B (101:53)

So masking is. And it's probably not the right way to describe it, but it's the act of acting normal. Normal. And that is how do I conduct myself in a social situation? In a way that other neuropithy people are going to, or that other people who are neurotypical are going to receive and accept it the right way. And everything you do in a social interaction, from waving my hands to taking facial expressions to tone of voice to posture, it's a huge contrivance. And it's work.

A (102:26)

Yeah.

B (102:26)

Comes natural to most people. It's just what they do. And cool people do it really well. But for somebody on the spectrum, you've got to fake it all.

A (102:36)

Yeah. Acting normal.

B (102:37)

There's a song by Rush, you know, the band Limelight, and it's written by Neil Peart. And I only speculated what people have passed on. So I've got a sense he was probably on the spectrum. But the line is something like, all the world's indeed a stage, and we are merely players, performers and portrayers each another's audience. And he talks at length in the song about not being able to treat strangers as friends and being able to fake an affect and all that. So it seems like he's struggling with masking a lot in the song. And I have no idea, but that was what I took from it.

A (103:07)

Yeah. You describe meltdowns as an overwhelming experience. Can you describe meltdowns? What typically triggers a meltdown?

B (103:15)

Generally it is. It's when you're emotionally overwhelmed to the point that you can't manage your behavior anymore. And so you see it in the movie Rain man when he's trying to get on the airplane and he's kind of forced and he starts losing it. That's a meltdown, or. I've seen it on. They did kind of a. Well, actually, probably the best portrayal I've seen in media is. What's a TV show where the doctor is autistic anyway? There's a TV show where a doctor is autistic and he's a surgeon, and he is eventually banned from surgery because of his autism, and he's always wanted to be a surgeon, and he has a complete meltdown. And it's a pretty good portrayal until it's television.

A (103:49)

So what is actually happening? Like, there's like a threshold you cross that it's Just like.

B (103:54)

Yeah, switch flips.

A (103:55)

It's like blue screen essentially.

B (103:58)

Yeah.

A (103:59)

Kind of for the brain algorithm.

B (104:00)

So switch flips, you go kind of a primitive brain. Your frontal cortex shuts down to an extent, I think. So you don't have the benefit of decision making and filtering. You're very reptilian brain in that state. And it's really a panic state. And so it's a panic and a fight or flight response to not being able to tolerate the current reality. And perhaps it's been so frustrating or you've been so randomized, or you had a bad travel day or an argument at work or whatever, it's added up to the point that something has now triggered you and your brain loses its ability to adequately moderate your behavior.

A (104:35)

What about love and relationships? What are some of the challenges of that? And there's a show love on the spectrum.

B (104:40)

I've heard of it. I've not seen it, but I've heard of.

A (104:43)

Because certain aspects, like literal interpretation of things, it just makes the complexity of relationships, of romantic relationships, even more explicit in that context.

B (104:55)

You know, I've been married 31 years and together for 37. So a long history there. And I think our first indication that we knew we were very different was we were sitting in the car one night out front of the house at dark, and across the street there's kind of a nice house. And it has these big brick pillars that are linked by like anchor chains and it forms a fence around the yard. And I'm looking at these things because they're about 2ft square, and I got a capstone and I'm like, you know, I wonder if they're hollow or are they backfilled, are they filled with concrete or what? And my now wife looks at me and she's like, what's wrong with you? Why do you have a place in your head that cares about that?

A (105:30)

Yeah.

B (105:31)

And I knew in the moment that I was passionately involved in caring and she was passionately involved in why would you even and worry about that kind of thing? New or very different.

A (105:40)

So, yeah, very specific, seemingly irrelevant details.

B (105:45)

But I was never good with people. I don't get it when people like me, I guess. And so I and my son is the same way because they all don't fall very far from three. And I got him a T shirt that says, if you're hitting on me, please let me know and be specific because I'm clueless. And it's very similar for me. I mean, I had to be around a long time and kind of grow on people because I had no game, because I had no ability to do the social dances that that whole thing requires. So my only option is to just be myself. And that works for some people.

A (106:15)

Were you able to say like, like I love you, that kind of stuff?

B (106:19)

Yeah, I mean, her family was way more open with that kind of thing than mine was. And so it was a growing period for me. But yeah, it's not a problem I have.

A (106:27)

Okay, all right. But, but it seems like unimportant. Like what is that actually accomplishing?

B (106:34)

Well, now we do a lot of, of affirmation and checking. Like in the last couple years we do a thing where she'll just be like, you good? I'm like, yeah. And there's two steps to that. There's the are you good? And then there's my response because if I'm like, yeah, she knows something's up.

A (106:49)

Yeah.

B (106:49)

And so there's always this pinging back and forth because there's not the ability to read people just from looking at them to know what's going on. So we have this explicit check mechanism, I think, where we've developed that.

A (106:59)

So there's a vast chasm between. Yeah. And again, that subtlety of human communication. You've written about the experience that people have of feeling, quote, a little bit autistic. Could you elaborate on this concept?

B (107:19)

Yeah, I think a lot of people, maybe 10 to 20% of the population is somewhere on the autism spectrum but isn't impacted by enough that it rises to the level of disorder. But they still have many of the characteristics that arise from autism. Autism. And I think if they can understand and identify and manage some of those behaviors in an optimal way, they can both leverage them to take advantage of some of the skills and mediate some of the deficits and problems that come with it. And I wrote it mostly for my kids because none of them, as far as I know, have asd. But they've all got certain aspects of my behavior that are particularly related to it. So I thought I'd write a little manual for them, basically.

A (107:55)

Why do you think so many programmers, like excellent, great programmers and great engineers are on the spectrum?

B (108:02)

I think it's that single minded focus and the ability to reduce a problem and to be ultimately curious about what's inside. Stuff that's been an obsession for me my whole life. What's inside. I got to take my mom's oven apart because I got to know how the flip clock works. And I think that's a good habit to have if you're going to be.

A (108:19)

A programmer and being willing, being excited to get into the details.

B (108:23)

Yeah, yeah.

A (108:25)

What's the cool thing you hope to program to build this year? What are you working on? So we got the RL learning how to play Tempest. Where are you on that, by the way? What's the ETA on success and dominance, like victory?

B (108:41)

Well, it's very close to working. I think now it's tweaking the model size and layers and stuff like that to get it to learn past the one threshold. But it's a couple thousand lines of Lua and it's a couple thousand lines of Python and they all interact and they all work. So it's like 95% of the work is done now. It's tuning hyper parameters. Hyper parameters and hoping for the best.

A (108:58)

So it's already a success in a sense. But like now you're seeing, like, how far can this go?

B (109:02)

Yeah, my goal was to be able to beat me.

A (109:05)

That's a tough. It is.

B (109:07)

But lots of games now are, you know, they play them better than humans, but maybe not games as complex.

A (109:13)

What other cool things are you working on? What you hope to build this year?

B (109:16)

The PDP 11 stuff. I'm trying to get what's called an RA82 drive. It's the big 14 inch monster that spins at 3,600 rpm and sounds like a washing machine. And then I'll find the controller card and write the code and integrate it into the driver and try to get that all working.

A (109:29)

What kind of code are you trying to run on it?

B (109:31)

I'm going to have to get the driver stack to work, so I have to incorporate the driver for it into the kernel.

A (109:37)

You built a machine recently with one terabyte of ram. How did that happen and why?

B (109:46)

So we have a project called GitHub Primes. If you just search for GitHub Primes, you'll find it. And it is a single set of prime number algorithms implemented in about a hundred different languages. So it's the exact same algorithm and we require that you follow certain rules to make it fair. And then you express that algorithm in whatever language you choose to the best of your ability. And we run a benchmark every night and we compile the results and find out which languages are fastest.

A (110:10)

Is this the one?

B (110:11)

Yeah.

A (110:11)

Oh, so this is so. Yeah, you got it. And this is what you're using this for?

B (110:17)

Yeah.

A (110:18)

Oh, so this machine runs that? Those tests?

B (110:21)

Yes.

A (110:22)

Okay, you gotta tell me about this project. This is an epic project. So you're comparing the performance of the different programming languages.

B (110:27)

You have all these languages, so they all get built into an individual Docker container and then they all run.

A (110:32)

This is an incredible project. This is really, really cool. It's really measuring the performance of the different languages. So what, what have you learned about which languages? Like who. Which language usually wins?

B (110:45)

Zig. I think right now, Zig. It does, it varies. People will make an improvement to the C, then it'll pass for a while and then the Zig guys will get angry and come back and make it faster.

A (110:52)

Zig Rust. C. C. Yeah. And what kind of code is being run? What's the piece of code that they're trying to run to measure the performance?

B (111:04)

So what they're doing is they're solving the primes up to 100 million as many times per second as they can in a 5 second second loop.

A (111:11)

So it's a loop. Got it. Over and over and over and over and over.

B (111:13)

Yeah. On all cores, across all CPUs.

A (111:16)

What about like how the program is written? Does that vary?

B (111:19)

No. So you can do anything you want, but it has to be a prime sieve. You're allowed to use one bit per integer at most, so you can't use a byte, which is cheaper and easier. There are a number of rules like that that you have to allocate the memory within your timed loop. And so we have a set of rules and we have some solutions that don't follow the rules, like the 6502 because you've only got 64K, you can't do 100 million SIV. So there's a lot of. Of solutions like that that we run as exhibition projects. But among the main languages they all follow the same rules and so it really should just be the how the algorithm is expressed in that language. And many of them use the same backend compiler. So it really is how you're expressing it and the limitations or the benefits of that language.

A (111:57)

Are there allowed to be multiple submissions per language?

B (112:00)

Yep. Yeah. So if you look in the C, there's like five I think.

A (112:03)

Okay. And they. Some of them might use different compilers or. No.

B (112:08)

Yeah. Some are gcc, some are C Lang llvm.

A (112:10)

I'm looking at a snapshot here from a couple years ago. Zig was at the top, then Rust and Nim Haskell. Oh no, this is not ordered by slowness or is it?

B (112:21)

Yep. So c would be 1.5 times as long as Zig.

A (112:24)

Wow. Okay. Fascinating. What's a super cool project?

B (112:29)

We've got in crazy languages like PowerShell, there's a version in Powershell and stuff like that.

A (112:34)

So. So this is automated, like in terms of organization of, like, how the submissions are done. There's a structure to it. That's cool.

B (112:40)

Yeah. There's two guys over in Europe, Rucker and Tutor, basically own this now. I started as just three languages. I did Python, C Sharp and C and I checked them in and I published the episode and then people started throwing more solutions in there and it just got out of hand, so I had to get somebody to manage that one and they've been great doing that for me.

A (112:59)

What's the happiest moment for you when you're programming and building a thing? Thing. Like, what do you enjoy most?

B (113:04)

I think the most fun for me is when I build something complex and I thought through how it should work and then I run it and it does work that way. That creates intense satisfaction. So seeing the results come out the way that I plan them and have it work. Because it rarely does the first time, but yeah.

A (113:22)

Or especially if it does work the.

B (113:24)

First time, I never trust that. I always feel like I'm missing something.

A (113:27)

That's true. But you know, with compiled languages, like with C, that's always a good feeling. You write a bunch of code, you compile it all compiles without warnings, without errors. It's a cool feeling. What do you think is the future of programming? So now I don't know how much you've got to really experience the impact of LLMs with CO generation. Do you use. Have you used cursor much? Cursor VS code with. With. With CO generation?

B (113:59)

Yeah, I've done a ton of it for this, the Python side, because I'm not great with Python and I'm kind of new to it, so I found it very helpful because I've learned a lot from watching the code that it generates if I don't know how to do something. Because if I write Python from scratch, it's going to be about four times as long as what the AI can crank out. Because Python can be pretty terse if you're good at it.

A (114:17)

Oh, that's cool. So just you, you essentially learn Python for this project?

B (114:21)

Yeah.

A (114:23)

So this is a good case study of like a great programmer in C quickly learning a language.

B (114:30)

Yeah, I'm vibe coding my way through it, I guess.

A (114:31)

Vibe coding your way through it. I mean, that is a really powerful use case to learn a language for if you're already a good programmer, to learn either a new language or a new way to approach a problem by having it generated. Because you already. You probably understand the Python code it generates.

B (114:49)

Yeah.

A (114:49)

Like without actually looking up any of the syntax.

B (114:52)

Yeah, it's all pretty self explanatory once you see it, but you know, creating it from a whole cloth is a little different, so.

A (114:57)

Yeah, but you still have to learn how to program in order to use it in that way.

B (115:02)

Oh, and to read it and to know what to tell it to do next and all that. Yeah. I don't think you can vibe code yourself if you're just new and haven't coded. But if you're a good programmer, AI can make you incredibly powerful.

A (115:13)

What do you think is the future of programming like 5, 10, 20 years from now? This whole process? Now vibe coding is kind of a fun meme thing because you still have to be. The people that don't know how to program it are just Vibe coding are almost entirely creating systems that are not usable in production. They're not. You can't. It's very difficult to create a product and the people who are already great programmers kind of vibe code just for the way that you're doing it. They're basically. It's just a fancy autocomplete and they end up editing it or it's a way to learn a new API or a new language or a new whatever specific use case or maybe a different kind of like a GUI component or something like that. But as they get smarter and smarter, we don't know where the ceiling is that might change the nature of what it means to be a programmer. So do you think about that?

B (116:06)

I do, I think. I don't want to say prompt engineer, but I think it's going to be something like that in the sense that if you're an architect building a bridge, at some point guys were down there welding beams together, but now you're dragging things around in AutoCAD and assembling from big free form sections and I assume that's what programming will be like. You won't be in there throwing individual lines of code around, you'll be moving components and interfaces and describing to the AI what those interactions should be and letting it build the components. But I think we're still quite a ways from it being able to whole cloth generate. You can't say give me a Linux kernel that's compatible with Linux, one day we'll be able to and it'll crank it out. But we're not there yet.

A (116:44)

Does it make you sad that were climbing the layers of abstraction so quickly. So you somebody that used to do machine code and then assembly, then C and C, that we're getting to a point where we're vibe coding with natural language.

B (117:00)

Yeah, I kind of came up at a really fortunate time, I think, because I had to come up with the technology over the course of 30 or 40 years. So I understand TTL logic and I can use AI to write code, and I kind of know all the pieces in between. There certainly are holes in my knowledge, but I think the only way to have got that level of knowledge or the completeness of that picture is to have lived it for that long. And it's going to be hard to duplicate that for people starting now.

A (117:26)

What do you think is the meaning of this whole thing of existence, of life, of whatever's going on here?

B (117:38)

Making cool stuff? I guess, fundamentally what I care about is being able to make complex things that are useful to other people, which leverages my abilities in a way that allows me to be creative and to create things that other people can use in a way that if I was limited to painting or sculpting or whatever in the classic arts, I would be hopeless. And so for me, that's really the meaning of life. And then maybe you raise a couple good kids to hand the baton off to.

A (118:09)

Yeah. And you've created a lot of cool stuff over your life that impacted millions, probably billions of people. And now you're inspiring. You're creating cool stuff for everyone to see on your YouTube and you're inspiring people in that way. So for everything you've done in the past and everything you're doing now, I'm a big fan. I'm really grateful for what you're doing and grateful that we got a chance to talk today. Thank you, brother.

B (118:38)

Thank you.

A (118:40)

Thanks for listening to this conversation with Dave Plummer to support this podcast, please check out our sponsors in the description. And now let me leave you with some words from Bjarn Strausstrup, creator of C and somebody who, by the way, I interviewed a long, long time ago. Episode 48 of the podcast. He said there are only two kinds of languages, the ones people complain about and the ones nobody uses. Thank you for listening and hope to see you next time. Sa.