John Carmack was the lead programmer and a co-founder of id Software, and the single individual most responsible for making fast real-time 3D graphics run on commodity PC hardware in the early 1990s. Working in C and tightly hand-tuned assembly, he wrote the rendering and engine code that underpinned the studio’s run of genre-defining titles: the smooth side-scrolling of Commander Keen, the ray-cast corridors of Wolfenstein 3D, the BSP-based renderer of Doom, and the first true polygonal real-time engine in Quake. Each pushed the limits of what a desktop processor without dedicated 3D hardware could do.
Carmack’s technical approach is documented in his own words across his archived .plan files, short developer logs he updated publicly throughout the 1990s. The community-mirrored archive at github.com/ESWAT/john-carmack-plan-archive collects these exports day by day across the Doom, Quake, and later eras, preserving his running commentary on optimization, networking, OpenGL adoption, and engine design decisions as he made them.
A defining part of Carmack’s legacy is his commitment to releasing id’s engine source code. In December 1997 he released the full Doom source under terms that became a GPL release, writing in the accompanying material about the renderer’s reliance on horizontal and vertical lines of constant Z with fixed light shading, and candidly noting design choices he would approach differently in hindsight. The repository at github.com/id-Software/DOOM preserves that release. He repeated the pattern with Quake, Quake II, Quake III Arena, and the Doom 3 engines, turning id’s commercial code into a teaching resource for a generation of graphics programmers.
In his QuakeCon keynotes, delivered on official channels over many years, Carmack spoke at length and without notes about rendering techniques, hardware trends, and engine architecture, making the talks a primary record of his thinking. The 2013 keynote is one example among many of these long-form technical addresses.
Carmack later turned his attention to virtual reality, joining Oculus VR as chief technology officer and continuing to focus on the low-level performance problems, latency, rendering, and frame timing, that had defined his career at id. His through-line across decades was a relentless focus on making interactive 3D fast enough to feel real on whatever hardware was actually in front of users.