It is a good thing to know your own weakness.

A newbie in programming often needs to ask a lot of questions/assistance and should. As they progress they will get to a point where they you have to decide whether to tackle the current problem alone (and take 3x as long) or ask for assistance.

The interesting thing to observe is when someone asks for assistance in solving a problem is what they do after its been fixed. Technical folks often still want to understand the reason the fix worked and the underlying concepts. Non-Technical folks are just glad the thing is working. If the problem happens enough, they might have a sticky note on their desk that has a routine for dealing with that specific error, but there is no true understanding of why it occurs, and a sort of lack of curiosity in that respect.

Does that make the non-technical person bad? No, not really UNLESS of course they are pursuing a technical career because then they are probably leeching off very technical people to survive.

Without a doubt, this works both ways to SOME EXTENT. A technical person left unchecked will probably not be the best business manager, but I think the redeeming factor for a technical person is that because they've developed a way to ingest a lot of detailed information they can often transform quickly into other roles.

Unless there is a whole lot of nuance/human factors, its always easier to deal with less complexity and detail than you are (used to/designed for), as opposed to more.