My last employer was like this. They had good people, but horrible practices that had become habit because of constant crunch-time.

During my interview I discovered that they did not use revision control. I agreed to take the job after they said they were going to start using a RCS.

Working there was a good experience for me as I was able to change a lot of their practices, and save the other developers future headaches. It felt good.

Other areas that were changed were increased use of reusable modules, extensive unit tests, increased awareness of security issues (especially sql injection), some WWW::Mechanize web testing automation, application monitoring, a group wiki knowledgebase, and an introduction to pair programming.

Since it is a perl shop I also encouraged them to take an active role at perlmonks, because my activity here has increased my perl knowledge tremendously. Providing the best answer you know to a problem can be very instructive, as it forces you to think through something that you "know", but might not know well enough to explain initially. And when others offer corrections or improvements to your answer you learn about the edge cases and internals.

In reply to Re^4: Revisioning systems and the lackof by imp
in thread Revisioning systems and the lackof by EvanCarroll

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.