Hacker News new | past | comments | ask | show | jobs | submit login

First off I hate the phrase "Rockstar dev" because it gives the impression that someone can be successful without the support of the team, which is wrong.

Second, I hear this extremely often: Rockstar devs don't like to mentor, Rockstar devs don't like to write documentation, Rockstar devs don't like to write tests.

At what point do you need to reevaluate your definition of a rockstar dev?

The hiring filter is a powerful thing. It allows you to find very special people if you know how to look. It's also a feedback loop. Getting momentum with a program like this is the hardest part. Once it's going it practically self sustains. The biggest part of your role becomes quickly firing any mistakes.




Related to this: know what you're hiring for.

Are you looking for someone who can parachute in with expertise on a specific tech and churn out working code themselves?

Or are you willing to accept more lag time and less initial code productivity in exchange for a deeper bench and sustainable team?

There are times and places for both of these developer types...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: