Dave Plummer traces his path from a Radio Shack TRS-80 to Windows Task Manager, Pinball and zip folders.
He started it at home as a side project he wanted for himself, reading stats from HKEY performance in the registry. Once brought in-house he could call internal APIs like NtQuerySystemInformation, making it fast and responsive. He prioritized robustness and small size over features; the original was about 87K and shipped in NT4.
Answered around 46:38Any API call that could take time, like a network path taking 90 seconds to time out, ran on a separate thread. He avoided linking the C runtime, saving around 96K, and called object constructors manually. Dirty bits on every row and column meant only changed cells were repainted, so it resized smoothly.
Answered around 47:34After reading the book Hard Drive about Microsoft, he searched the registration cards from his Amiga shareware HyperCache for Microsoft email addresses and cold emailed three or four people. Alistair Banks connected him with Ben Slivka, who did a phone interview and hired him to work on MS-DOS for the summer.
Answered around 20:17He wrote Visual Zip at home as a shareware shell extension around 1995, motivated by a photo of a house and red Corvette taped to his monitor. Microsoft called to discuss acquiring it, not realizing he worked there. He accepted, bought a used 93 Corvette, and features like encryption and multi-volume support were removed.
Answered around 1:02:38John Vert, who wrote the NT blue screen, chose it because the MIPS firmware he was building on used that color scheme, and so did his editor, Visual SlickEdit. That way he could code, boot, crash and reboot all in the same colors. The Windows 3 blue screen is completely unrelated.
Answered around 1:07:45Two things accumulate as computers run: memory gets used and not freed, piling up on the heap or swap file and making things sluggish, and code drifts into rare states developers didn't anticipate or test well. Rebooting gives a fresh state with no memory leaks, so it covers a lot of sins.
Answered around 1:08:28Late in the XP ship process, the plan was to adapt Office activation code to Windows, but the owner had slipped it repeatedly. Plummer, known for fixing things quickly, was asked to finish it. With help from the DRM team and researchers doing product key math, they delivered it in time for XP.
Answered around 54:47Of about 12 claims, two stuck: the expired 30-day trial reminded users once a day, which the AG called spam, so it became once a week with one-click uninstall; and shipping a physical disk for $3.95 or $4.95 was a pre-checked default, violating negative affirmation billing rules in Washington.
Answered around 1:18:38He kept the original game's state engine as a black box, but his port had a bug that drew as many frames per second as possible, up to 5,000 on modern computers. Physics were interpolated 5,000 times per second instead of about 30, producing different physics. That bug has since been fixed.
Answered around 52:34Add asserts organically while building code, not later. Assert things you know cannot be true, like a pointer never being null or a count staying below twice the byte width. A firing assert is a bug, not a warning, and it does you a favor; people who avoid asserts fearing they'll fire are wrong.
Answered around 45:26“At the time, it was the single most potent assemblage of smart people that I've ever been a part of.”
“So if you use 10K needlessly, every machine in the world now has 10K less.”
“Yeah, I would say that 20% of my professional life has been creating and 80% has been debugging and fixing.”
“I don't assert things that I hope aren't true.”
“Lex AI Dave Plummer.” https://media.blubrry.com/takeituneasy/content.blubrry.com/takeituneasy/lex_ai_dave_plummer.mp3. Transcript summary by WhipScribe, https://whipscribe.com/transcript-pages/lex-ai-dave-plummer.html.