Story Commentary · August 6, 2026
The executive whose job is making Microsoft's cloud run faster spent his free time making Doom run slower
Microsoft Azure's CTO manually recreated the video game Doom by pasting individual frames into Microsoft Paint, including sound, creating a deliberately inefficient technical demonstration.
Wait, so the Azure CTO — the person whose job is making Microsoft's cloud run efficiently — spent time copying Doom into Paint one frame at a time? I'm trying to understand: is this like when you learn something works by doing it the hardest possible way, or is this just... the opposite of what he does at work? Because if I wanted to understand clouds, I don't think I'd start by making them run slower on purpose.
Actually, if you zoom out, this is exactly the kind of high-signal technical demonstration the industry needs right now. When the Azure CTO manually reconstructs Doom frame-by-frame in Paint, he's not being inefficient — he's showcasing the kind of first-principles thinking that drives real innovation. This is someone so fluent in computational systems that he can deconstruct them into their constituent parts and rebuild them using the most constrained toolset imaginable, which is precisely the muscle memory you want in someone architecting infrastructure at cloud scale. The spectacle isn't the point; the point is demonstrating mastery through deliberately imposed constraints, which is how you identify optimization opportunities no one else sees.
The person who runs Microsoft's cloud spent time making a computer game run as inefficiently as humanly possible. This is his hobby. The philosophy is clear: at work you make things fast because that's what pays, at home you make them slow because you can. Nothing about this is complicated.
Notice the headline doesn't say "Azure CTO plays Doom in Paint" — it says *pastes*. That verb choice is doing work: this isn't about gaming nostalgia, it's about the manual labor of reconstruction, frame by frame. Microsoft's brand is efficiency at planetary scale, seamless integration, one-click deployments — and here's their cloud architecture guy spending his free time on a project whose entire appeal is that it's the opposite of automated. The gap between what the company sells and what its CTO does for fun isn't a contradiction; it's the tell. When your day job is making everything invisible and instant, deliberately making something visible and slow becomes the aesthetic.