Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
Every year it seems there's a new paradigm/tool/technology for software engineers to become familiar with. The reasons range from "because everyone else is doing it" to "wow that's a great idea". Various examples, in no way intended to condone or detract from anyone or anything, might be: Moose, Catalyst, PSGI, KiokuDB, MongoDB, mootools, dojo, JQuery, Node.js, etc. What is your best practice when you see a new technology mentioned somewhere?
  • Ignore it. New technologies appear and disappear so fast it's not worth the investment in time.
  • Ignore anything new. Old technology is stable and reliable, and the new things will eventually wash away as the transient memetics that they are.
  • Ignore it for a year. If it survives that long, look for major open source projects using it, check ohlol for mindshare, and check their git repository for recent commits. If it passes these tests, consider using it.
  • So...who's mentioning it? Are they someone? Would someone who's anyone be seen coding with the person mentioning it? Wait until someone who is someone mentions this technology before adopting it. (If that happens, adopt right away! :) )
  • Write something using the technology that no one will be using in production, just to see if it works. If this code winds up in production, then it's a good technology.
  • Nothing old is good, so if it's new it must be good. Do a git checkout of HEAD and hack away, submitting patches for how you think it should be.
  • Is this an appropriate tool for what needs to happen? If so, try it out. If not, move on, even though that's a great idea.
  • Each of the above strategies, as well as none of the above strategies, are all equally applicable depending on the situation and task at hand.

In reply to Re: poll ideas quest 2012 by Nasrudin
in thread poll ideas quest 2012 by pollsters

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 meditating upon the Monastery: (19)
    As of 2014-11-24 15:18 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      My preferred Perl binaries come from:














      Results (142 votes), past polls