Game Development Community

Keeping change logs and learnt knowledge

by David Andrews · in General Discussion · 01/19/2009 (7:57 am) · 1 replies

Strange title I know but I couldn't think what else to call it.

How do people record the knowledge they have picked up when creating games - so they do not have to remember again?

How do people record the changes as they go through the development of a game?

I have searched for things like project management software but much of this focuses on scheduling on when projects would be finished.

I am looking more for a resource repository (for images, scripts etc) and knowledge base of changes I have made and knowledge I have picked up through my developments.

Does anyone know of anything that can do this?

#1
01/19/2009 (9:02 am)
I have found the best place to keep scraps of project information, is near where it belongs. What i mean is, if im changing C'code or writing scripts i leave detailed comments about what im doing, sometimes explaining what im trying to do in case i come back months later to revamp some ugly unreadable code.

I keep my project design notes in a hodgepodge bunch of simple .txt files saved also in my /torque folder.

I keep all my raw artwork inside Torque also, the mesh art right next to the DTS, DIF and QUARK/Constructor files, photoshop's .PSD with the final .jpg/.png and uncompressed .wav right next to the .ogg. Its so much simpler to just backup my /torque partition and know i have everything taken care of.

As far as remembering info from the forums, a quick shortcut also saved in the torque folder, sometimes renamed like "how to fix that annoying glitch" for clarity.

I do keep a journal and have a notepad next to the computer that i 'clock in' and 'clock out' when i start and end my time working with a note about when i started/stopped what i completed, and what i was doing when i left. This helps me optimize my time, and keep on track in the case i take a few weeks off. Its also helpful when working in a team, so its easy and fast to communicant with them about whats going on, and about how long to expect tasks to take.