In the end, if we are going to code to the lowest common demoninator, we can get rid of strict, lexicals, and subroutines. :)

i think this is what i was getting at. while i won't pretend to say my skills hold a candle to yours, i can tell by looking at the old codebase at this company that i'm the most experienced person that's been there ... i know i need to do more to document things, but i'm always stuck in the trenches.

i do tend to write a ton of little toy scripts to make sure function X does what i thought it did ( my homedir is full of them ), and refer back to them when needed.

i want to leave behind a way that people can learn something as well as have tight code that works properly.

just to clarify -- i don't think mainentance programmers have to be of a 'lesser' skill set than the original developer. i'm also a big fan of the Kernigan quote mentioned in another reply, and it has proven true at this job, because i've fixed longstanding bugs that the original (no longer at the company) developer just couldn't fix.

overcoming the managerial resistance is the biggest issue at this place. i've had a hell of a time convincing him that we need things like *shared* libraries, better source control, etc. because he's more concerned with ease of tossing a client their code if they leave than with making the developers' jobs simpler and easier.


In reply to Re^2: "advanced" Perl functions and maintainability by geektron
in thread "advanced" Perl functions and maintainability by geektron

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!
  • 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, details, 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, summary, 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.