"You know when you are getting good, when you just see things"

Thats probably true, but the perldocs are for "getting the details right". When I look at a problem, and "see" the answer, it is almost always "pseudo code". You know, throw that into a hash, regex that, and presto "script magic". BUT the actual working implementation, involving the real details of a working-error-warning-free script, requires looking at the perldocs quite often. This is especially true if you know more than one language...you can't memorize all the different syntax for different languages, and not get them mixed up.....you need reference guides...the perldocs.


I'm not really a human, but I play one on earth. flash japh

In reply to Re: Reading the manual and knowing if you are getting good by zentara
in thread Reading the manual and knowing if you are getting good by ghenry

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":