in reply to Re: Popularity of Perl vs. availability of Perl developers
in thread Popularity of Perl vs. availability of Perl developers

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

  • Comment on Re^2: Popularity of Perl vs. availability of Perl developers

Replies are listed 'Best First'.
Re^3: Popularity of Perl vs. availability of Perl developers
by dragonchild (Archbishop) on Sep 26, 2005 at 13:23 UTC
    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.

    A further part to the story, which will help explain it. The IT director, who'd been at the company for about 2 years to the DBA's 5, was the one who'd been quibbling over the $4k. The DBA's manager had been pushing for $65k, hoping to get $60k. When the DBA put his resignation in, the #2 in the company called him into his office and asked about why he was leaving. The DBA laid it out and the #2 said "I can give you $65k right now, no questions asked." The DBA refused, citing the IT director as the issue. The raise issue had been a test of the director's commitment to his people. He failed.

    In the year since this happened (last November), I know of 4 people in the department of 20 that have left, including myself and the DBA. Last I heard, another 6 were looking. All have cited the director as a major reason for their decision. *shrugs*


    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

      Thanks for the update -- that helps flesh out the story a little better.

      I wonder, of course, why the company kept the IT Director on after that. And over $4k? $4k is nothing, for a company of that size.

      The IT Manager should probably have sold it as "The DBA wants $60k -- he's probably worth lots more, because of his history with the company; why not raise him to $60K and give him a $5k bonus?" That way he'd have been a hero to both the company and the DBA.

      Another quick story: my wife used to work at a company where she had a great manager and loved going to work. That manager moved on to something else and the Manager From Hell arrived. Morale plummeted, and the group started losing people.

      My question is, where is HR when all this is going on? When a group goes from normal attrition to All Hands Abandon Ship, doesn't it occur for HR to look into what recent changes have taken place? And what about exit interviews? That information is gold for an ogranization -- the soon-to-be ex-employee has nothing to lose and can unload (within reason, of course).

      Oh well. Stuff happens.

      Alex / talexb / Toronto

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

Re^3: Popularity of Perl vs. availability of Perl developers
by adrianh (Chancellor) on Sep 26, 2005 at 12:58 UTC
    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.

    ... and have a process that ensures that business critical knowledge is always in more than one head. Having a Truck Number of one is always bad.