Thanks. I made a few minor changes based upon your feedback. I also didn't like my discussion of the "fat comma", but I was struggling between how I would normally write the code and how I would write it so a beginner can understand it. That's the simplest way that I came up with, aside from the "fat comma" distraction. It did bug the heck out of me, though, and you're quite right to point it out.
And as for why I don't explain each lesson in such a way that the code can stand on its own: each lesson would take five times as much space and be that much longer to write. And how far back would I go? In order to make this reasonable, I went a fairly standard pedagogical route and assumed that for each lesson, the student had X amount of knowledge coming in and if they get to a particular lesson, anything they didn't know is either explained in a previous lesson, falls under the rubric of "required knowledge to study this" or I have links and suggestions for where they can acquire the knowledge. I'd love to have each lesson stand on its own, but it would just be too much work.
Thanks for the input!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||