If you aren't sure which way to do something, do it both ways and see which works better.

Honestly, I spend very little time thinking about past events, and I certainly don't have them ranked in any way. I look back and think that I have done a lot of good work over the years, but I am much more excited about what the future holds.

You can prematurely optimize maintainability, flexibility, security, and robustness just like you can performance.

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 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.

Sometimes, the elegant implementation is just a function. Not a method. Not a class. Not a framework. Just a function.

The cost of adding a feature isn't just the time it takes to code it. The cost also includes the addition of an obstacle to future expansion. ... The trick is to pick the features that don't fight each other.