If you're willing to restrict the flexibility of your approach, you can almost always do something better

An interesting question: is it easier to motivate a learned individual that never does anything, or educate an ignorant individual that actually produces things?

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.

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.

It is difficult to make good scalable use of a CPU like you can of a graphics card. You certainly don't want 'better or worse' physics or AI in your game

The speed of light sucks.

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.