I probably should spend more time on my own code, perhaps. But this site has certainly proven a pleasant distraction from staring at unchanging error messages.
There is a saying in the literary world that disparages writers who produce more than they read. I think that concept applies equally well to writers of code: one who writes more code than they read is a fool.

Yes, spending time refining your own code and learning through example and trial is exceedingly beneficial. But, reading and understanding others' code is essential to improving your programming ability. Helping those less skilled than you is useful as well, as it helps solidify a concept when we explain it to others.

Participating in PerlMonks has done more for my Perl ability in the year or so than reading books and trying to write applications did for the previous three. This is only partly resulting from having Sought of Perl Widsom; it's much moreso learning from meditations, trying to answer simple SoPW questions, trying to understand the more advanced questions (and, more importantly, the answers), and so on. Never underestimate the value of exposure to others' work!

<-radiant.matrix->
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet

In reply to Re: A work of art by radiantmatrix
in thread A work of art by hesco

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.