As a programmer of 20+ years thru Basic, COBOL, Fortran, C, REXX, C++, Java with smatterings of C-shell, Bourne shell, AWK, SED and more, & just 1 weeks aquaintance (all be it heavy hours and with real goals), I am finding this transition the worst ever. Maybe I'm just getting old.

I saw people advocating the PerlDocs........I cannot agree. I have so far found them far to terse, full of religious terminology (magical, autovivication, globbing etc.) and (as someone without much unix background) far to full of explainations that refer to (what I assume) are common, well-known Unix terminology, references and explaination-by-comparison with Unix concepts, to be of much value to me.

See Perl IO::Dir or IO::File (actually anything in the IO::* packages) for examples of this. Try and imagine these pages as explainations, if the Unix stuff isn't part of your experience set.

I suggest (and will be doing myself) getting the books first.

I then agree with most of what other people have been saying ...Set him writing *real* code ASAP and give him the time and space to experiment. Don't give too long a timescale for the first project up-front......no pressure means no incentive in my experience.

In reply to Re: Teaching a CompSci student by BrowserUk
in thread Teaching a CompSci student by astaines

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.