<?xml version="1.0" encoding="windows-1252"?>
<node id="980280" title="Re^4: How to read CPAN documentation" created="2012-07-06 10:25:23" updated="2012-07-06 10:25:23">
<type id="11">
note</type>
<author id="352046">
ww</author>
<data>
<field name="doctext">
... and then, for [perl.j|OP]'s next career (or retirement), you can use the knowledge and skills that will take a major part of your lifetime to absorb to write the kind of sketchy documentation that only another long term, hard-core, CS-degree-holding, uber-geek can decipher.

&lt;p&gt;AnonyMonk's observation about reducing your need for the docs, "&lt;i&gt;on a daily/weekly/monthly basis&lt;/i&gt;", could be read (admittedly, not as AM 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.&lt;/p&gt; 

&lt;p&gt;Sorry, while I agree that most of the links can be useful... and are responsive -- in a fashion -- 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.&lt;/p&gt;

&lt;p&gt;Here in the Monastery there have been several interesting discussions (for example, [id://963544]) of aspects of this problem -- some from the POV of the developer, like the one cited, and some from the perspective of the learner ( check with [Super Search] ) and not a few that may seem merely tangential at first (cf: [id://366615] and 3 or 4 followups thereto).&lt;/p&gt;</field>
<field name="root_node">
980242</field>
<field name="parent_node">
980270</field>
</data>
</node>
