John Carmack Quotes

The Xbox 360 is the first console that I've ever worked with that actually has development tools that are better for games than what we've had on PC.

The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.

The situation is so much better for programmers today - a cheap used PC, a linux CD, and an internet account, and you have all the tools necessary to work your way to any level of programming skill you want to shoot for.

In the information age, the barriers [to entry into programming] just aren't there. The barriers are self imposed. If you want to set off and go develop some grand new thing, you don't need millions of dollars of capitalization. You need enough pizza and Diet Coke to stick in your refrigerator, a cheap PC to work on, and the dedication to go through with it. We slept on floors. We waded across rivers.

Personally, I’ve always been of the sleek and minimalist design school: make sure the core play is consistent and strong, then let that idea play out against different environments and challenges, this tends toward focusing on bio-mechanical twitch responses, audio-visual awe, and leaning more toward general strategy and tactics development over specific puzzle solving.

Because of the nature of Moore's law, anything that an extremely clever graphics programmer can do at one point can be replicated by a merely competent programmer some number of years later.

Nvidia's OpenGL drivers are my 'gold standard', and it has been quite a while since I have had to report a problem to them, and even their brand new extensions work as documented the first time I try them. When I have a problem on an Nvidia, I assume that it is my fault. With anyone else's drivers, I assume it is their fault.

I think a lot of people may take some heart from this: a lot of the math, the heavy math in projective geometry, [...] took me a long time. There were many many years, a decade, when I was considered this graphics guru genius, when I really couldn't do from scratch [...] the mathematics that underpins a lot of that. But slowly, eventually, with a couple decades of experience, most of it did eventually sink in on me.

It is hard for less experienced developers to appreciate how rarely architecting for future requirements / applications turns out net-positive.

Helping people directly can be a noble thing. Forcing other people to do it with great inefficiency? Not so much. There isn’t a single thing that I would petition the federal government to add to its task list, and I would ask that it stop doing the majority of the things that it is currently doing. My vote is going to the candidates that at least vector in that direction.

Sharing the code just seems like The Right Thing to Do, it costs us rather little, but it benefits a lot of people in sometimes very significant ways. There are many university research projects, proof of concept publisher demos, and new platform test beds that have leveraged the code. Free software that people value adds wealth to the world.

A large fraction of the flaws in software development are due to programmers not fully understanding all the possible states their code may execute in.

It's a good thing Doom 3 is selling very well...

These are things I find enchanting and miraculous. I don’t have to be at the Grand Canyon to appreciate the way the world works, I can see that in reflections of light in my bathroom."

The Escalation programmers come from a completely different background, and the codebase is all STL this, boost that, fill-up-the-property list, dispatch the event, and delegate that. I had been harboring some suspicions that our big codebases might benefit from the application of some more of the various “modern” C++ design patterns, despite seeing other large game codebases suffer under them. I have since recanted that suspicion.