numinary1
Joined 11 years ago
Joined 11 years ago
For me, changes were the key. Burnout melts away. But you can burn out in any role. If you have the skills to do tech work, try to keep them alive. Coming back to hands on tech work is incredibly refreshing. So is leaving it behind for awhile when you've reached the burn-out point.
Corporate culture embraces the notion of management as a profession. I think programming would benefit greatly from more of a tradecraft model, where leadership is provided by the master practitioner rather than the professional manager. In the alternate universe that's how we do it. The bottom line productivity boost is awesome. I don't know if it scales, but I don't care to scale.
-- 63-year-old full-stack web and machine learning programmer...living the dream
Here's how I think it works. Skilled interviewers are biased toward rejecting candidates based on any negative impression. Structured interviewing has the same effect. It's the precision versus recall tradeoff. For this use case only precision matters. Extremely low recall is fine.
Also, in the GPA prediction example, the interviewer is penalized for predicting a low GPA for a person who performed well. But in hiring, there is no penalty for failing to hire someone who would have performed adequately.
(Yes, I understand there is an implicit assumption in my argument that candidates are not in short supply, but that's usually true, certainly at Google)