As my tutorials are "a problem-solving approach", I really want to make sure I adhere to this, and help newbs learn how to do problem solving. (You know everyone who asks "What's the point of math?". So you learn that you can figure things out on your own with concentration and studying!

Right now my tutorial for Episode 2: Making a Shmup basically says "Here's how you'd create and load a map file". After reading through random mishmash problems people have elseware (ie "Why can't you figure out how to turn a 1D array into a 2D array??"), I'm starting to think this isn't such a great idea; make 'em work to figure out how they'd load in a map. :P
Or do you guys think it's basic enough that I should go ahead and show them how they can use a while loop to load in a map file and store it? And then use a for loop to draw it to the screen?
Anyway, I'm having a hard time figuring out how to present it such that they try to figure out how to achieve some goal, without telling them the answer, but still having enough content to actually be a guide and not a test.
Then again, I've been sick on and off for a month and I'm exhausted, so my own problem solving skills are functioning at about half capacity right now. @_@
Ugh, if nothing else, I should have a lot of theory and not so much code. This tutorial is supposed to be library independent anyways.