Actually that's not a downside! PerlMonks SoPW provides a pretty fair slice of how information is presented in the real world. Very often "programming" problems aren't, they are really problems elucidating the actual problem then solving that (which often is fairly trivial).
Following along on the process of digging out the information needed to describe a a problem then solving it is not at all a bad way of seeing how that process works (or doesn't work). Writing the code to solve the problem then comparing it to the (often) many answers provided by others with a range of skills using a variety of techniques provides much better insight than the (generally) single "answer" provided in a book or similar resource. Being able to follow up a solution with questions about how and why makes learning in the PerlMonks context way more effective than any formal self study course or even than many class.
Perl's payment curve coincides with its learning curve.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
