3 ms·
I think that the idea that people who see development as safe career are the most incapable is just wrong. Someone stable that does what needs to be done even w
by watwut 7y ago
I think that the idea that people who see development as safe career are the most incapable is just wrong. Someone stable that does what needs to be done even when it is not fun sounds good to me. Large parts of projects are not fun nor challenging - they are work that needs to be done with good quality.
People who see their jobs as safe careers are routinely good at those jobs.
And conversely, I have met people who talked about passion and seemed passionate and had all the right opinions. And they were not good simply because they would loose interest when it stopped to be fun or somehow never finished anything that was medium sized, were disorganized or demotivated easily.
- hinkley 7y agoI don't think we are necessarily in disagreement. What we want and what we need are often at odds, perhaps nowhere more clearly than in the way we select new team members. I speculated on why our interviews are so insane, and just kept pulling that thread. What I omitted from GP was this thought: I don't know if we are right to want this, or if the world could have ever let us have it anyway. There are other measures of 'contributor' that we weed out with our interview processes. Some of those are qualities that working programmers are more likely to have. For instance, work-a-day developers tend to be less susceptible to hubris. Sometimes when you have a problem to solve, you want the no-bullshit person to do it. It's way easier for me to talk someone out of Imposter Syndrome or at least convince their boss to ignore it than it is for me to dial in the degree of Kruger-Dunning my faster-talking coworkers are covering up.