Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

Comment on

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

I think I understand what you're going through. I've also been at clients that for one reason or another decided it would be better to re-invent the wheel, then did a poor job at it. It's not just Perl, either. I've seen it with many other languages and technologies. There seem to be a few common reasons (excuses) I run into:

  • We're unique. Nobody else in the world does anything like what we do, so we need new wheels that are rounder than everybody else's.
  • Job security. All the code was written by a genius guy who left us six months ago. Don't touch it or it'll break.
  • Budget justification. We had to find something for everyone on the staff to do so we could get funding next year.
  • Control issues. If everything isn't built in-house, one day it could go away. (This is related to the "but who would support it" non-issue.)

Each of these has a reasonable response, but you need to phrase it such that someone with a business perspective will understand you. Probably the strongest argument would be to remind them that CPAN can affect budgets and delivery schedules very positively!

It appears you've grown disenchanted enough to want to throw in the towel. I don't know your circumstances, so maybe that is the right thing to do. But if it's just a question of "better late than never", I encourage you to go ahead and try to make your case. If you need specific arguments, post again. Many of our senior monks are both articulate and wise, and would probably be only too glad to help.

In any case, hang in there.


In reply to Re: The worst amputation possible: Perl proper as Open Source software by VSarkiss
in thread The worst amputation possible: Perl proper as Open Source software by princepawn

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 perusing the Monastery: (11)
    As of 2014-12-18 21:22 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

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





      Results (66 votes), past polls