I would say it's not very important that these Java guys suck at graphics algorithms if they are great at rapidly building web applications and that's what their line of work calls for. They may not be uber-coders, but they may have a lot of very satisfied users who appreciate their talents.

For those who long to earn more programming street-cred, there are always new areas where modules have not yet been written. Everyone knows something they think should be on CPAN that isn't there yet. Or else they know a feature that an existing module needs. Or a set of unit tests that an existing module needs. There are lots of ways to get experience without re-inventing wheels.


In reply to Re: Re: Re: Code re-use: productivity gains vs. skill deprecation by perrin
in thread Code re-use: productivity gains vs. skill deprecation by Phemur

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.