Going the extra step, here's a few topical links (in no particular order) found using Search Search to find nodes containing the words "teach teaching:"

There are many others, but I think the most obvious relevant point is to choose projects that are important to them. In fact, I would make it a team effort, e.g. hold a "meeting" where the lot of you get together and make a list of various projects that they'd like to learn and to build.

Also, there are a lot of applications that come to mind just from the bits you've posted. For example, you mentioned:

I guess the main point is to find out what problems they would find interesting to solve and then work in the skills they need to learn: Basic Programming Skills, Database Design, Careful Design, Research Skills, and so forth. You can cloak these in Gift Lists, comic book libraries, action figure tracking, viewing logs, video tape libraries, or whatever.

In my experience, programming requires a lot of problem solving and critical thinking. If you can get them doing that--and taking direct action to solve their own problems--then you'll help them develop some basic skills they'll need to survive later, whether they turn into programmers or not.

Finally, make sure they're always accomplishing something. Personally, I find training works much better when you're working toward concrete goals. For example, I've taught a variety of coursewares for certain programming languages and my students generally seemed to prefer those that focused on skills that they could then apply to their work and needs.

(BTW, I suggested the meeting earlier because there is generally an element of interaction in all jobs. For example, you may be a lone gun, but you deal with people all the time. If you can help them learn how to deal with other people fairly, then you'll be helping them avoid some of the problems you ran into.2)

Oh, yes....wattle time3....

--f

Footnotes:

1 - Yes, the root note has been reaped, but there is some good discussion in the orphaned replies.

2 - For everyone else: In case you hadn't noticed, I've known growlf in RL for a very long time. So I'm allowed a little gentle ribbing. :-)

3 - ObRef (See #2).


In reply to Re: Teaching The New Generation by footpad
in thread Teaching The New Generation by growlf

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.