Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

There is nothing wrong with re-inventing wheels. Re-inventing wheels is an excellent educational exercise and a fine way to learn how wheels work. One of the most effective way to learn how some high-level construct works is to have to take care of handling all the low level stuff yourself. It will give you an appreciation for how other wheel implementors did it (or possibly point out some problem in their implementations) and highlight the difficulties of making wheels that work with both racing bicycles and earth-moving equipment. And who knows? you may even invent mag-lev transport.

The problem is with saying "Hmm, I need a new set of wheels for my car. It can't be that hard, I'll whip some up in my basement." and ignoring all the research and testing that has gone into make wheels better over long periods of time, when really, all you want is a new set of wheels. It could work, but you'll probably spend more and take longer than just buying something from your local wheel shop. Most likely, you'll end up with something that doesn't work very well or even ends up hurting you or someone else.

Even more annoying to their fellow mechanics is when someone re-implements a wheel, then loudly proclaims that their wheel is "TEH BEST WHEEL EVAR!!1!11" and everyone else should immediately switch to using their wheel and that anyone who points out that this new wheel has only been tested on a 1957 MG midget, at 25 MPH, falls off randomly and requires buying a whole new set of tools to change the tires is met with "YOU AR TEH SUCK, FIND SOMEONE ELSE TO REPRE#SS, YOU ELETIST SNOB!!!". It may actually even be better, but without compelling evidence, few people are likely to switch.


In reply to Re: Reinventing the wheel by thundergnat
in thread Reinventing the wheel by cavac

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others pondering the Monastery: (7)
    As of 2014-12-25 18:33 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      Is guessing a good strategy for surviving in the IT business?





      Results (161 votes), past polls