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

Comment on

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

One thing you might consider is putting together a workshop (say about 3 hours) for your coworkers. Get management to sign-off on the idea so it is an official workshop.

Spend a good deal of up front time going over basic coding practice and style (consistent indentation, strict, warnings, checking return values) then move into more specific areas. Compile up a list of example code (or pseudo example code) from problems you've helped with in the past --- so the examples are targetted at the kind of things they are actually doing --- show the problem code (no names), and your version, and most importantly, why and how your version is an improvement.

You may even be able to coax management that a once a month afternoon programming workshop is a good idea. These wouldn't necessarily be be in a presentation format as the above, but more open discussion of current projects and troubleshooting code (but always be prepared with your own examples of code that needs improvement, kind of along the lines of MJD's 'red flags and repair' articles on --- you'll need these if no one brings any code of their own, or perhaps just to get the ball rolling). Such a monthly workshop gives both your coworkers and yourself a good chance to keep learning and improving, and can certainly improve productivity (that may help you sell it to management). If management won't bite, see if your coworkers are interested in informal (voluntary) version of the same. If they aren't interested in putting in some time and effort in self improvement, you needn't feel compelled to keep helping them now (imho).

In reply to Re: Should I write your code ? by danger
in thread Should I write your code ? by ChOas

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, 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
  • 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others contemplating the Monastery: (7)
    As of 2018-05-24 16:07 GMT
    Find Nodes?
      Voting Booth?