Interesting story -- and a sad one, too.

I wonder how the DBA tried to sell his $8k raise, what salary he started with, or how his annual raises progressed. Because it seems to me he had a dynamite job, and with the right sales pitch could have been making a six figure salary. And the company is now paying for trying to save a $4k raise.

Something similar happened to me -- I was the lone developer left from a development team of a dozen, making $34K. When my boss announced he was leaving, the owner called me into the bosses office and asked me how much I was making. I told him, and he immediately gave me a raise to $40K, to give me incentive to stay.

It worked -- I stayed another two years, and was able to support and even add a few features to his desktop publishing product (Laser Friendly's The Office Publisher, if any of you remember the late 80's). So, for an additional $6k per year, over about a 2 1/2 year period, he bought continued technical support for a cranky old scotch-taped togther piece of code written in Turbo Pascal. Without it, he would have been stuck with a piece of code going nowhere.

This should be a lesson to business owners: don't leave yourself too thin when it comes to crucial business IT infrastructure. Maybe your DBA's being a prima donna -- but do you want to ignore their request for a raise? Better to get someone cross-trained on the database, and then ease the troublemaker out.

$120/hour, 2_000 hours in a year makes $240K -- and after all that, this person's finally up to speed. Oops.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds


In reply to Re^2: Popularity of Perl vs. availability of Perl developers by talexb
in thread Popularity of Perl vs. availability of Perl developers by aufflick

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.