comment on

My list is:

Balance is everything
Why and how to use the CPAN

And all of their dependencies.

By the time a Perl hacker reaches the point where they can use the CPAN effectively they have significant technical skills and cultural know how.

When said hacker is then starting to pass good judgement on effort vs. gain, complexity vs. simplicity, and all of those topics we have such a hard time with I think that J. Random is ready to take the final journey. This stage is much more intangible than any other learning stage, and is often walked alone, but arguably it's the stuff that makes you into a "real" programmer.

I don't think this journey ends, btw ;-)

We have a word for these kinds of musings in hebrew - it's the combination of the roots for philosophy and flatulence.

-nuffin
zz zZ Z Z #!perl

In reply to Re: top ten things every Perl hacker should know by nothingmuch
in thread top ten things every Perl hacker should know by apotheon

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.


Just another Perl shrine
	PerlMonks