I really need some more RAM for my computer. No really, I only have 512MB and I thought that would be enough - however a combination of a 2500+ file project in Microsoft Visual Studio 2003 and the Source engine (which only needs to be run once before rendering my computer pretty unusable until I next reboot) gives me plenty of time to sit around waiting for my computer to respond to input.

Anyway, currently my work is in the glamorous area of bug-fixing. While most of the main features are now in, a lot of them need either fixing or adding to in some way or other. I know some of you will be wondering "why not add all the features first then iron out the issues", and for you people I have this professionally prepared graph.


As you can see stuff gets harder and longer to fix the longer you take to get round to doing it. For example, fixing a typo in "The Enemy has your flga!" done at the start of the graph would be pretty simple. I'd know which file to go to and just change it. However doing it 7 months down the line I probably wouldn't remember what file it was in, where in the file it was and what the correct spelling of 'flag' was anyway (maybe).

By the way, that blip at the end isn't actually something meaningful, I just slipped with the brush tool.

Bugfixing is generally quite boring, as a lot of it is stuff like "The nailgun is firing 0.08s too slow" or "the civilian has grenades that's not right is it". We have a whole bugtracker with all the open (ie. not fixed) bugs listed, along with comments & details of who is working on fixing it. I'm running a private bet with FryGuy (private as in, he doesn't know about it) that by the first release there will be at least 250 bugs listed and hopefully fixed. This is something to do with him saying that he thought there be too few bugs to justify about 80 million bug categories but I can't really remember.

Anyway that wasn't quite as FF-progress related as I had hoped, still hopefully next time.