comment on

I agree with the principle, but...

There is value in reinventing the wheel when it comes to learning.

For newbies in particular, it is sometimes a good idea to understand the mechanisms behind what they are trying to do. The depth of understanding that results increases their PERL expertise overall and will make them a better user of whatever the feature/package is which has already been written.

Additionally, it is often only near the end of writing some code that you realise that there was a better way to do it.

Rather than start by loading lots of packages, I often start with a top down approach, and then look for a package/function/feature when I get to a point where it looks 'obvious' that there is a suitable wheel to reuse.

Even when I have found a suitable package, I will then look through some of the keys pieces of the package so I can understand how it is achieving the functionality I am looking for.
This leads to an overall better understanding.
--
Brovnik

In reply to Re: Assume that Perl has what you need by Brovnik
in thread Assume that Perl has what you need by petdance

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.


Syntactic Confectionery Delight
	PerlMonks