Crash Course in Game Programming
I have a project "Computer Game Programming" which I am writing to introduce programming to possible students.
My approach is to have very simple code that does simple visual animation; then in the documentation describe in detail what the code does as I introduce the programming concepts that the code uses.
So instead of tutorial style to build up the code, as many younger students have a short attention span and will bail quickly, I deliver the working program and then break it down. If they run the demo and like what they see, maybe they will take some time to study the explanation.
Writing the course documentation is the challenge, I want to allow for someone with no prior knowledge of programming to "get it". I find that it's necessary to be highly redundant, in order to avoid ambiguity.
Let me know what you think. Any editing suggestions would be highly appreciated!