Sometimes projects end smoothly, without any problems or drama. But sometimes… there’s a monkey wrench thrown into those plans.

My primary goal when I began work on this project was to be able to get extremely in-depth with my work.

Once Ratchet & Clank: Size Matters started to get good reviews, the big marketing push was only a matter of time. Not only was the game doing well, but now we’d get to see television ads and giant posters with our game on it. It was extra special for me because, since Ratchet & Clank has always been about the gadgets, clips of what I had contributed to game were going to end up on TV.

During the development of a new game it’s not uncommon for a level or two to occasionally fail to load. Maybe there’s some outdated built data on someone’s machine or perhaps a change went in that hasn’t been tested in every level yet. There’s all kinds of problems, and if you are on debugging machine, you’ll see the callstack and be able to tell the right person that needs to fix it what’s up. But artists, they don’t have a debugger, they don’t use a callstack. They rely on the output of warning messages to help them know who to go to when a level fails to load.

And Ricardo, one of our programmers, was getting a lot of visits from the artists.

You see, it just so happened that the last message that was seen by the artists when a level …

Ratchet & Clank: Size Matters was my first game I worked on in the game industry. The first game I made content for. The first game that hit shelves. For many, many reasons this title is special; perhaps most importantly because of the excellent people that I was able to work with and learn from.