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.
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.