The Accidental Influencers of id Software
Long before anyone knew what a "blog" was, John Carmack was accidentally inventing tech journalism in a 256-character Unix text field. His .plan file updates — raw, unfiltered streams of consciousness about graphics programming, server architecture, and whatever pizza he'd ordered for the team — became required reading for thousands of aspiring game developers who treated each update like scripture from the digital mountaintop.
Photo: id Software, via i.redd.it
This wasn't intentional content creation. Carmack was just using a standard Unix feature designed to let users share brief status updates with colleagues. But when you're building Doom and Quake while the entire gaming industry watches your every move, even your grocery list becomes Silicon Valley gossip.
The Unix Feature That Launched a Thousand Careers
The .plan file was originally designed for academic Unix environments where professors and researchers could share their current projects with colleagues. Type "finger [email protected]" and you'd get a brief summary of what that person was working on, when they last logged in, and maybe a pithy quote or two.
For most people, .plan files contained thrilling updates like "grading papers" or "office hours 2-4 PM." But when id Software's programmers started using them to document their work on revolutionary 3D engines, finger requests became the internet's first subscription service.
Websites like "Blues News" and "Shugashack" built entire businesses around scraping and republishing .plan file updates from game developers. These weren't official press releases or marketing copy — they were raw engineering journals that gave unprecedented insight into how groundbreaking software actually gets built.
The Daily Pilgrimage to Digital Mecca
By 1996, checking John Carmack's .plan file had become a daily ritual for anyone serious about game development. His updates covered everything from OpenGL optimization techniques to philosophical musings about software architecture, written in the same matter-of-fact tone whether he was discussing texture mapping algorithms or his lunch order.
The technical depth was extraordinary. Carmack would casually drop insights about graphics programming that wouldn't appear in academic papers for years. He'd debug complex rendering problems in real-time, sharing both his failures and breakthroughs with anyone curious enough to run a finger command.
Other id Software employees like John Romero and American McGee maintained their own .plan files, creating a multi-perspective documentary of one of the most influential game development studios in history. Fans could follow the entire creative process of games like Quake and Quake II through these daily journal entries.
The Unfiltered Truth About Software Development
What made .plan files revolutionary wasn't just their technical content — it was their complete lack of corporate polish. These weren't press releases or carefully crafted blog posts. They were working notes from programmers who happened to be changing the world.
Carmack would complain about compiler bugs, celebrate breakthrough moments, and share the mundane frustrations of software development. Readers got to see that even legendary programmers spent most of their time debugging stupid mistakes and fighting with tools that didn't work as advertised.
This transparency was unprecedented in an industry built on marketing hype and carefully controlled information releases. Game companies usually treated development details like state secrets, but id Software was accidentally creating the blueprint for modern "build in public" culture.
The Fan Sites That Became Media Empires
Websites dedicated to aggregating and analyzing .plan file updates became some of the internet's first successful independent media properties. Blue's News, run by Brian "Blue" Hook, became the CNN of gaming news by obsessively tracking developer .plan files and providing context for casual readers.
These sites developed sophisticated scraping systems to monitor dozens of developer .plan files simultaneously, alerting readers whenever important figures posted updates. They created the first real-time news cycle in gaming, where information traveled from developer's keyboard to fan community in minutes rather than months.
The comment sections on these sites became legendary for their technical depth. Professional game developers would engage directly with fans, creating impromptu computer science lectures that were more valuable than most university courses.
When Transparency Became a Competitive Advantage
id Software's radical transparency through .plan files wasn't just good for fans — it became a powerful recruiting tool. The best programmers in the industry could see exactly how id Software approached complex problems, making the company irresistible to top talent.
Other game companies tried to replicate the magic by encouraging their developers to maintain public .plan files, but most attempts felt forced and corporate. The authentic voice that made Carmack's updates compelling couldn't be manufactured or managed.
The .plan file culture also created unprecedented accountability. When you're documenting your daily progress for thousands of readers, it becomes much harder to waste time or make excuses for missed deadlines.
The Death of Digital Intimacy
The .plan file era ended gradually as the internet became more commercial and companies became more protective of their intellectual property. Legal departments started reviewing developer communications. Marketing teams wanted consistent messaging. The raw, unfiltered insights that made .plan files valuable were sanitized out of existence.
John Carmack's last significant .plan file update was posted in 2004, marking the end of an era when the internet's most influential technologists shared their thoughts directly with anyone curious enough to ask.
Modern social media platforms promise the same kind of direct access to influential figures, but the signal-to-noise ratio is incomparable. Twitter threads and LinkedIn posts are optimized for engagement rather than insight. The deep technical discussions that flourished in .plan file comment sections have been replaced by emoji reactions and character limits.
The Legacy of Accidental Journalism
Today's tech influencers and "thought leaders" are essentially trying to recreate what John Carmack did accidentally in the mid-1990s: share authentic insights about cutting-edge technology development with an engaged audience. But what took zero effort in the .plan file era now requires content calendars, engagement strategies, and personal branding consultants.
The .plan file format was perfect because it was constrained. Limited space meant every word had to count. No rich media meant the focus stayed on ideas rather than presentation. The Unix finger protocol was inherently egalitarian — anyone could access anyone else's .plan file without algorithms or paywalls determining what they could see.
Every modern "build in public" startup, every developer blog, every technical newsletter owes a debt to the programmers who accidentally invented tech journalism by simply documenting their work in a 256-character text field.
The internet became a more connected but less intimate place when we stopped fingering each other's .plan files. Sometimes the most profound innovations happen when brilliant people aren't trying to change the world — they're just trying to share what they had for lunch.
