Monday, 26 October 2009

Fellow Developer Blogs

Since this blog is mostly about art I thought I'd share some links to a few blogs by other developers for those interested in what game development is like. There are quite a few developers blogging so this is just a small sample, there are a lot more out there that I haven't had time to read yet. Without further ado...

The Further Adventures of Oddbloke 

A quite funny blog written by a programmer. Quite varied and this post does describe what it's like to work in a studio quite well:

What Your Fellow Man is Capable Of

This is written by a gamedesigner and has some very insightful articles on what makes games fun. He also talks about how you can make a game more fun by paying attention to what's been done before and what actually works as well as other random bits and bobs


Excellent blog about life and work for a westerner working in Japan. Sadly he hasn't updated it in a while but there is an extensive archive that is well worth reading if you are the least interested in working in Japan.

Double Fine 

Not really a blog but Tim Schafer posts a lot of random stuff on the Double Fine News section which can be quite amusing. For example this post which shows some of his rejection letters and the completely awesome application that got him a job at Lucas Arts.

Warren Spector 

Warren Spector is a legend and sadly he doesn't update all that often but it's still worth a look.

Raph Koster

Raph Koster has been working in this industry for a long time, mostly relating to Virtual Worlds and MMOs.


Makers of Uplink, Darwinia and more talk about the development, the business of being an independent developer and they are very open about the cash flow problems they have faced and how they overcame them. Some really cool R&D there too!

There are tons more out there so go forth and explore the links from the blogs listed above!

Late additions:

Joel On Software

The article linked above is titled "12 steps to Better Code" and while it's not games industry specific, it can probably benefit programmers, if nothing else as ammunition when talking to managment about improving procedures etc. Worth a read even if you're not a programmer since it will give you a better understanding of what they are up to over in the code-bay and why it might be a bad idea to interrupt them when they are working.

No comments:

Post a Comment