Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There are a lot of code in open source projects, looking at all of the code is time consuming and can be confusing to a novice like me. Are there any sections of open-source projects that should be focused on?

What should I focus on when I look at code?

I'm asking this in general because if I ask this specifically, the question will only apply in one or two projects rather than an entire group of projects ranging in different types of games and difficulty.

share|improve this question
Funny you ask this, I was just looking at the Triple A source code and didn't know where to start... – Russell Apr 12 '12 at 14:01
-1 ... you focus on the parts of the code that are relevant to whatever problem you're trying to solve? – Tetrad Apr 12 '12 at 15:57
Some projects have a section/part of the documentation designed to give new developers an overview over the project. Unfortunably, documentation is often neglected. – sarahm May 4 '13 at 10:35
up vote 6 down vote accepted

I'd recommend running Doxygen: Here is a list of the features: Doxygen's uses the Graphviz tool kit to generate include dependency graphs, collaboration diagrams, call graphs, directory structure graphs, and graphical class hierarchy graphs. I find these types of diagrams helpful when trying to understand a large codebase.

share|improve this answer
thanks, but in addition, why wont the doxygen work with project folder rather than just working with the sub-folders – Blue Apr 14 '12 at 18:53

Focus on what you're trying to get from the code. Are you looking for examples of design, for a working sample of how to do a particular thing, or anything specific like that?

Outside of that, have a look at the more general things around the code. Is it readable? Can you follow the program flow? How well commented it is? Do the comments provide useful info in addition to the code, or do they just repeat what is already evident from the code?

Other general factors might include: does the project actually compile as released (a surprising number don't)? What are the dependencies? What is the end-user installation experience like?

You might also find it useful to step through the code in a debugger to get a closer look at what it's doing and how it's doing it.

share|improve this answer
I'm looking for examples. It's hard for me to look at too much code because I won't understand the code without having to look at it closely. I'm trying to figure out the important parts code in any project. – Blue Apr 12 '12 at 18:46

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.