There are some (see: Gamedev.net) that think OGRE isn't all that good when it comes to OO design due to "heavy use of singletons." It is a little annoying, and there probably is a better way to design some things it does, but it's still an okay learning source.
The thing about studying the source for an entire game is that you can see how it all fits together, instead of guessing why a certain system exposes one interface but not another. Just be sure that, no matter what source you study, you keep thinking to yourself "I would have done it this way instead, I wonder why they didn't?"
What source code is better for studying?
- Firestryke31
- Member
- Posts: 550
- Joined: Sat Nov 29, 2008 1:07 pm
- Location: Throw a dart at central Texas
- Contact:
Re: What source code is better for studying?
Owner of Fawkes Software.
Wierd Al wrote: You think your Commodore 64 is really neato,
What kind of chip you got in there, a Dorito?
- AndrewAPrice
- Member
- Posts: 2299
- Joined: Mon Jun 05, 2006 11:00 pm
- Location: USA (and Australia)
Re: What source code is better for studying?
Reading code doesn't always mean you will be better at writing code, or understanding code. If I were to scroll through the source of a major open-source software, it would just go in one side of my brain and out the other. What I recommend doing is starting a small project to challenge yourself, for example a simple video game. When you reach a problem, search for solutions online, and the code you come across will be more beneficial to you because you have a reason to understand it, learn from it, and most importantly apply what you've just learnt.
The second point I'd like to raise is learning a programming language does necessarily make you a good programmer. Just the same way as learning an new natural language instantly make you an author. The language is just a tool for telling the computer what to do.
Programmers have particular field(s) they focus on, either by choice or it emerges naturally as you choose more challenging projects to focus on. For example, to be a Compiler Programmer would focus on the latest techniques for optimization, implementing modular back and front ends, creating parsers, etc. An Artificial Intelligence Programmer would get intimate with different theories of neural networks, neuron layouts, and training methadologies.
So my advice is to start out with writing small projects that interest you. They don't have to be technically challenge but rather theroetically challenging, and you'll find the technical skills will develop naturally.
The second point I'd like to raise is learning a programming language does necessarily make you a good programmer. Just the same way as learning an new natural language instantly make you an author. The language is just a tool for telling the computer what to do.
Programmers have particular field(s) they focus on, either by choice or it emerges naturally as you choose more challenging projects to focus on. For example, to be a Compiler Programmer would focus on the latest techniques for optimization, implementing modular back and front ends, creating parsers, etc. An Artificial Intelligence Programmer would get intimate with different theories of neural networks, neuron layouts, and training methadologies.
So my advice is to start out with writing small projects that interest you. They don't have to be technically challenge but rather theroetically challenging, and you'll find the technical skills will develop naturally.
My OS is Perception.