I wish you good luck !

Even to only define the 'planning before', could take a whole book.

I remember loooong time ago I was told :
"Use organigram(ordinogram) to build your program."
I was then said :
"think procedural".
Lately the hype was :
"everything is an object, think in terms of interaction between those objects".
(And I don't speak about other exotic scheme : predicate,recursive solving...)

Even for the naming convention things changed :
The hungarian was once good, it's now bad...

Of course everything isn't so clear,
but the fact is that there isn't to my mind one way to code :
There are several, each best suited for a specifical kind of problem...

I fear that you can only teach basics things :
loop, I/O, branching, error handling, different type of variable, pointer/reference...

Learning how to program can only be, IMHO, a long process,
made of experiments, other coders comments, mistakes, book reading...

Now, please don't see it as an "It's impossible" answer,
but rather as "give them THE BASIC and THE WILL TO LEARN"

Anyway knowledge transfer is an interesting field,
and I long to read here what you (perl mongers) think.
I'd really love to see a method to learn how to programm,

---

---

• 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.