My short visit to video game industry

Ever since I got my first computer, a Commodore 64, I decided that I want a job as a guy who writes computer games. Well, I got a job in video game industry when I was 28 years old. By that time, I had a Master’s degree in computer science and seven years of experience in traditional software industry.

It was like dream coming true. Finally I could live my dream and program cool games for the rest of my life. I was so excited about the opportunity that I did not even care about the open office. There were no doors. Not even cubicles. Programmers in one area, graphic designers in one, and game designers had their own area. You could easily hear the game designers talk from the programmers’ corner. Obviously the managers of that company had never heard of the book Peopleware, which should be mandatory reading for every single manager and programmer in every company that does software.

My title was Generalist Programmer, because I did not have any special game programming skills like graphics or AI. I thought I would write code for the game the company was developing, and pick up graphics and AI skills a long the way. What I did not know that a really big part of Generalist Programmer’s duties were related to version management. I would spend a week every month merging our changes to the latest version of the 3D engine. I probably should have asked what my tasks were going to be, but I was so excited about the job that I did not do that.

Actually my only interesting task during my time there was creating a plugin for 3D Max, but I could not really focus on the task, because of the environment; People were having loud design sessions 20 inches from my desk, which made concentrating a bit difficult. Of course, I could have used headphones and listen to music to block out the noise, but listening to music actually prevents people from coming up with creative solutions, because the brain is already occupied with the music. I read this in Peopleware, and I think it might actually be true for me.

The other, more experienced, game programmers were not doing that much coding either. They were mostly using the editor that came with 3D engine and putting pieces of the game together. No-one actually did heavy programming full-time in that company. I knew that if the other guys were not programming that much, I would never be able to just program all day long, which was the only thing I wanted to do.

The situation was not as bad as it might sound, but it was such a big shock for me, because I had created these illusions in my head that game programming would be the coolest job ever. I came crashing down from my dreams. It was not at all what I imagined it to be. The pay was also pretty bad compared to regular programming jobs. After three weeks I felt so bad that I had to leave. One evening I came back to work after everybody had left and left my key on my desk. My boss and his boss were out of town, so I just sent an email explaining the situation. My boss called me the next day and I explained the reasons why I left.

Looking back at situation, I probably should have talked about these things immediately with my boss, but I didn’t. I just wanted out. My dream was crushed. I just wanted to write software. I am really happy that I tried to pursuit my dream. It did not work out for me, but at least I gave it a shot, albeit a short one.

  • Share/Bookmark

Leave a Reply