No wrong. Everyone should rubber duck their own issues and debugging before bringing it to the team. Otherwise you just end up with learned helplessness and overburdening more experienced Devs.

Because see teamwork goes both ways. You need to be valuable to your team otherwise you are just a leach.

Debugging is a skill like any other that needs to be practiced. The first step in that is having the confidence to know you can find the solution. If the first inclination is always to “go to the team” you will never gain that confidence.

This doesn’t mean you never seek help but it means you identify the appropriate amount of time per problem to investigate the problem before seeking outside help.

That amount of time is dependent on a lot of things. Your skill level in that area vs others on the team, knowledge areas of the team, availability of the team and impact of interruptions, project timelines deadline, your own curiosity.

See what the difference is here, this actually requires MORE team integration than the “take it to the team” approach. It requires good useful communication at stand ups, paying attention at stand ups getting to know your teammates backgrounds and skill sets.

As senior dev and lead I would never refuse to help anyone on my team find a solution to a problem but the very first thing I’m going to ask you to do is show and tell me what you have already tried.

If one of those isn’t waking away coming back and just reading you code one line at a time in detail looking for mistakes (or heaven forbid RTFM or Google it), then that’s the first thing I’m going babysit you to do. I’m not going to do it for you and if I see the problem I’m not going to point it out to you I’m going to take you down the long path on how you could have figured it out on your own.

Now I’m fine doing that once, twice or even a half dozen times it’s great to learn but if that becomes a regular occurrence you are going to start getting assigned very boring and simple work, something you can handle because clearly you cannot handle complex problems on your own.

Now if that’s the kind of dev you want to be that’s fine but your usefulness to the team is limited and frankly you are letting your team down.