(Before you panic, i am still gainfully employed and have no reason to doubt this will continue for a while.)
I was recently contacted by a recruiter who found my résumé on the Web. The dotcom's job req began: "You're smart, you're fast, and most importantly, you always get it done. Admit it, you're a rockstar."
I had to suppress the urge to backhand my craptop's screen. So instead i wrote this and asked the recruiter to pass it onto the responsible party:
This is embarrassing. I wouldn't hire someone who calls himself "a rockstar" any more than i'd want to work somewhere that looks for one. It sets the wrong tone for this sort of work, implying that this person is going to hog the spotlight. The only worse term i can imagine is "cowboy".You know what? Systems administration is hard work, and it gets harder every day. Companies want you to know at least a bit of everything and to be awesome at something. The line between network and systems administration has blurred, and the line between DBA and sysadmin is blurring as well. Staying current is a tough chore, especially when you've been working all day. So spare me your "rockstars" because the last thing i need is to deal with some strung-out narcissist with root access.
no subject
Date: 2009-05-23 04:50 am (UTC)The one thing I've learned in project management and software design is that a surprisingly large amount of the success that a project has, assuming that it has clearly-defined requirements and a finite scope (which is my job) depends upon one other person besides me: the rockstar programmer. In my career, I have had three rockstar programmers working for me, and I wouldn't trade 'em for anything. I've known plenty of programmers who were simply good at their jobs, but there are a rare few who not only understand the requirements at first glance, but who then, in less time than you estimated, produce better software than you asked for, accounting for edge cases that you didn't even think of.
And these people are worth every penny of the $100/hr they cost. Why? Because they're rockstars.
no subject
Date: 2009-05-23 05:08 am (UTC)I agree. Also most "rockstars" have "been there done that" which cuts loss time/money on maintenance, enhancements, bugs, or capacity issues.
IMO, true "rockstars" also have REAL WORLD admin/engineering experience across the entire software stack that is being used.
Unfortunately most senior programmers are not rockstars which can greatly demoralize a company.
no subject
Date: 2009-05-24 06:56 am (UTC)no subject
Date: 2009-05-23 09:15 am (UTC)1) Failing to anticipate requirements, thus inducing a situation that requires the last-minute heroics that so impress. "The Team got us into this mess, but I'm the lead rockstar -- I'll fix it!"
2) Leaving an enormous mess for the next guy to clean up, while the Rockstar moves on to the next rockstar-task.
3) Knowing exactly how to play the political games necessary to claim other's work as their own.
There are a few more I could probably think of from years of experience in dealing with self-proclaimed rockstars, but it's late, and I need to get my rockstar beauty sleep.
no subject
Date: 2009-05-23 04:48 pm (UTC)See, those aren't rockstars, those are just mediocre programmers with an overdeveloped sense of self-importance.
You don't get to proclaim yourself a rockstar, you arrive at that label by other people comparing you to other good programmers, and finding you not even on the same scale.
no subject
Date: 2009-05-23 09:05 pm (UTC)A genuinely good programmer knows damn well that he knows very little, and would take umbrage with being called a rockstar.
no subject
Date: 2009-05-23 03:36 pm (UTC)