Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
Hey there peaceful friendly monks,

I need a quiet haven after all the unpleasantness here at work. Here's my story:

At work we are having this ongoing rift between different groups of coders - I'd group us into two categories:

1) If it ain't broke don't fix it
2) code can always get better

. We code three different databases, all of which share minimal (if any) code. It was then suggested by a manager-type that we explore ways we could share more of our code since the functions of the databases are very similar. We thought we should start by all using the same routine to connect to the databases. easy enough, right? uh, no.

Some of the coders say that they are fine with doing this. But their actions say otherwise. They just want to use the current code.

Other coders have grown very resistant to even the idea of change. They don't see why the code should change to something else. They have this mindset that nothing will ever change, and that making the code more abstract (ie. separating out the config from the Perl) is useless to them.

Anyway - here's my question(s) -

I know we all face this challenge of not reinventing the wheel. Have you managed to get your coworkers to share their code more - from using libraries to setting standards. How do you get the word out about new code you've written? How do you get it so that everyone doesn't just rewrite the code in the style that they prefer? I know that I have done that myself . I was thinking that if our group had more shared coding standards, (and more documentation), then maybe I would have used the already existing database connection code.

But everything is done in this hacked, do-it-my-way style. Also, do you have any advice for me on how to convince coworkers that sometimes change is ok?

thanks rachel

In reply to code-sharing at work. by geekgrrl

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 musing on the Monastery: (6)
    As of 2014-08-23 15:53 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      The best computer themed movie is:











      Results (174 votes), past polls