3 ms·
That's a classical political problem. Sometimes it's good to be the problem solver that takes care of things but often you end up being the sucker to do things
by maxxxxx 9y ago
That's a classical political problem. Sometimes it's good to be the problem solver that takes care of things but often you end up being the sucker to do things nobody else wants to do. And you get no credit.
I had this once with answering questions for a new dev. He asked a lot of stuff. I first answered happily but after a while I realized that he didn't even try to find out things himself but instead asked me immediately. So I stopped answering and promptly got a complaint from his manager for not helping with critical stuff. Thank God I got support from my team so it was no problem.
Lesson learned: Be selective in taking on things that are not directly your job or could be done by somebody else. Set some boundaries.
- hnzix 9y agoMy approach to learned helplessness is to still assist the person but don't give them the final answers or do it for them. Instead, ask them leading questions. "Why do you think foo is failing? What happens when you add some debugging here? Have you read the foo section of the docs?" That way you can't be accused of not helping, and the person is developing their critical thinking skills. Unfortunately our Western educational system is still based around rote learning, which can really hamstring some folks when converting facts into actions.
- maxxxxx 9y agoThere is also a difference between learned helplessness and laziness. In my case it was plain laziness
- aytekin 9y agoThis is very common mistake junior developers make. My approach is to ask them only ask questions after 10 minutes of research. If they have spent 10 minutes trying to find an answer, they are allowed to ask that question.