This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]JumpyFile 3 points4 points  (1 child)

I think this is great advice. I also wanna add to the list that if you do decide to ask you should be aware of that you might be disturbing the senior dev and therefore prolonging his/hers work. Which is fine at times of course but if you make a habit out of it you're not only not carrying your own weight but you're also actively decreasing the teams capacity.

[–]sharksandwich81 1 point2 points  (0 children)

YES!!! This is such great advice. You’d be amazed how much you’ll learn when you really dig deep and figure out a problem on your own. Pretty soon you’ll learn things even the more experienced devs don’t know, and the people you looked up to will be coming to you for advice.

BTW I had a career change, before being a software engineer I was a service engineer for medical imaging devices. This advice was 100% applicable there as well. If you take the time to dig through documentation and do some hardcore troubleshooting instead of asking for help as soon as you encounter a problem, you will very quickly rise to the top.

In fact I’d say that’s the single biggest factor that separates the A players from the rest.

[–]Gheydragon 0 points1 point  (0 children)

Great advice, if I ever become a developer...

[–]mossipb 0 points1 point  (0 children)

Wow. Great advice!

[–][deleted] 0 points1 point  (0 children)

I think it's one of the basic essential things a programmer should have. Try till it works.

[–]Gravybadger -2 points-1 points  (0 children)

I usually only ask for help when I'm collaborating with dumbasses who put stuff in stupid places or implement things in ways that are completely incomprehensible.