4 ms·

Maybe it does to some people, but I use the term "Rockstar" to connotate: - highly productive - gets features shipped (avoid analysis paralysis) - features rare

Maybe it does to some people, but I use the term "Rockstar" to connotate: - highly productive - gets features shipped (avoid analysis paralysis) - features rarely have bugs - features rarely have to be refactored when we scale - code is easily maintained by other engineers If such a person were to also work 80+ hours a week, then they would just get that much more done. But I know plenty of people who meet the criteria without working long ours. I think some people who aren't "rockstars" try to correct for it by working longer hours, but I don't think that's what it's meant to imply. Most productive engineer I've ever worked with was "older", had a kid, and a family. Easily as productive as the rest of the team combined.

krstck 12y ago
> I use the term "Rockstar" to connotate: - highly productive - gets features shipped (avoid analysis paralysis) - features rarely have bugs - features rarely have to be refactored when we scale - code is easily maintained by other engineers Then just say you want those things! Why use meaningless fluff words that do nothing but attract a very specific demographic and turn the rest of us off completely?
ramblerman 12y ago
I'm not sure if you're a recruiter or work with bringing new talent into the team. But when you say "I use the term "Rockstar" to connotate", don't forget many might not interpret it that way. You could be having the opposite effect by using that term in ads. My experience is anecdotal, myself and my peers, but I skip the rockstar/ninja/gurus ads pretty quickly unless the tech/description draws me back in.