I recently read The Psychology of Computer Programming by Gerald Weinberg. It was an awesome book and provides some incredible insights into the mind of the programmer and successful programming teams.

Regarding the irreplaceable programmer, this is a Bad Thing for everyone involved. It keeps the programmer stagnant, mucking around in the same old code-bog. It keeps management fearful of losing the programmer, taking away some of thier motivational options. As Weinberg suggests, when a programmer becomes irreplaceable, it's time to replace him.

The company may lose some productivity in the short term, but in the long term it will be better for all involved if they let him go. The company will have learned from its mistake and will always keep more than one programmer trained on the system. When the programmer finds new employment, he will be faced with a new system to learn and hopefully this will bring about a new wave of motivation to increase his knowledge.

The fact that he's well liked makes the firing more emotionally difficult, but a good manager should be able to put those emotions aside and make the right decision for the company.

--Dave

In reply to Re: (OT) Motivating the Unmotivated Programmer by redsquirrel
in thread (OT) Motivating the Unmotivated Programmer by Ovid

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.