I wish I'd been on your class when I was 12. Your lesson plans are pretty good, but perhaps there are a few too many concepts for the first Item. If you are good at explaining those concepts and your class is intelligent enough, that's fine, but the first Item looks a little heavy to me. Personally, I would look more at variables first than code re-use.
When I started programming all I had was the manual of my dad's C=64. As I didn't have an IQ of 200 I was always amazed when I read about games programmers, like the Darling brothers, who were publishing their own games when still at boarding school. I pretty much gave up on programming as a hobby until my late teens when I finally understood the DATA lines in C=64 programs and I could suddenly design my own sprites! Unfortunately I didn't persevere with collision detection. To my shame it took until 2nd year at university to understand how to program things, not just a single sprite, on a frame-by-frame basis. We were in pairs for a practical class and my partner had a loop to decide what to do with each sprite at each frame.
How can you feel when you're made of steel? I am made of steel. I am the Robot Tourist. Robot Tourist, by Ten Benson
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|