Thread: Learning curve

I am reading a book on 2D game programming, and I can't remember much of the code, although I understand how it works and am able to do some simple modifications, though I'm stuck on one, probably a bit more advanced one now.

I am wondering how usually the process of learning a programming language goes - is it okay if I don't remember most of the code and just understand the way it works. I'm not really good with memorizing "static" things usually - for example at school I always can retell a text from two A4 pages by reading it once for an A or A+, but I can't recall mathematical formulas by reading them 20 times. Same goes for the code.

As for my current knowledge (if that matters) - I know the basics of C++, a bit of C and learning Win32 basics from a book about game programming. My ultimate goal is to create some nice little games (I have a lot of ideas in my mind) that people could enjoy. Although I'm a bit afraid of graphics design at the moment, but for now - I want to learn the code.

I think programming a simple game to start with is a good way to learn concepts but ultimately you will have to read more academic books to really understand the language and learn it. There is little benefit to memorizing syntactical sugar or this CRT function or that function b/c all of that can be looked up in API docs, etc. I think it is far more important to know which CRT functions to use in which situations as opposed to knowing all of them by heart. When I program I normally have the Direct3D SDK open, the Windows SDK open, documentation for any 3rd party libraries I may be using open, and several websites. Knowing what sprintf() does and when to use it is far better than just memorizing sprintf() as a function without remembering what it does or what it is for.