3 ms·
> Spend more time trying to figure things out for yourself before asking for help. Isn't this obvious and don't most developers want to do this? I work with s
by buckbova 12y ago
> Spend more time trying to figure things out for yourself before asking for help.
Isn't this obvious and don't most developers want to do this?
I work with someone who basically refuses to figure things out for himself and goes from person to person trying to get us to tell him how to develop something. Eventually he throws so much cruft at a project until it works.
It's been years and he asks the same questions. I've told the others I work with to stop helping him. Grow or die.
- monocasa 12y agohttp://thecodelesscode.com/case/100 http://thecodelesscode.com/case/100
- seanwilson 12y agoThere's a difference between not asking for help and asking for too much help though. Frequently a team member can save you hours by giving you a few minutes of help e.g. maybe they know about a useful library for something when you were about to implement your own one. That's not the same as asking for help every time within minutes of encountering a tiny problem like your example though. I agree that's not a good thing to do.
- deleted 12y ago[deleted]
- jquast 12y agoYou are correct, and this is a pervasive problem. When I was a tutor, I learned to answer their questions not directly, but showing them how the material they already have can supply it. "Well, let's start with the index, <turns to back of book>, ok, let's read chapter four from the top, together ..." So the same thing could be applied, "Lets go to your desk, let's look at the manual together, why don't we google together" etc. The lesson to the student is, "I could do this faster myself", and they'll stop asking you unless they really need it.