comment on

Your observation about reducing your need for the docs, "on a daily/weekly/monthly basis", could be read (admittedly, not as you intended ) to suggest that there's a substantial amount of time required just to learn to read the docs en route to so mastering their content as to make them unnecessary.

Sure, if you're purposefully trying to read between the lines

Sorry, while I agree that most of the links can be useful... and are responsive -- in a fashion

Well, that is how you become a seasoned programmer, so you can just go on CPAN and pick it up in no time

-- to OP's original question, they set the price of learning the answer too high, IMO, for a learner with a specific project in hand.

If you think so, why don't you lower the price?

perl.j has history of both generic and specific questions, he knows how to SOPW, he wasn't asking for help with a project, he merely alluded to it.

In reply to Re^5: How to read CPAN documentation by Anonymous Monk
in thread How to read CPAN documentation by perl.j

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.


P is for Practical
	PerlMonks