1. Draw two circles.
2. Draw the rest of the owl.
This is a common problem in art, music, sport and programming - you have an expert trying to teach newbies, and they say "just do this". The newbies have no idea how to begin to do it and the expert knows it so intuitively they cannot break it down further. Everyone ends up staring blankly at one another.
Getting people past that point seems to be a skill of its own. Certainly it's not been easily packaged for programming. Learning involves a lot of guided experimentation, and keeping the student's morale up is just as important as the material itself.
My father is a very talented pool player, but he was not the best teacher until my own skill became pretty considerable.
He's so far removed from the things that are important to beginners. He says "you have to hit that shot with a medium-power, really good draw stroke." They have no real idea what medium power is, and no idea what a stroke really is, and possibly can't draw the ball.
It's possible he's just a poor instructor--that's probably not very related to his own playing ability. Some people can convey complex ideas in a very simple manner, and I think they make the best teachers.
I remember very well the painful process of my dad trying to teach me to drive stick shift (on his new truck). He never mentioned that the clutch had a catch point (that wasn't all the way at the floor), but gave instructions that really hinged on that fact (give it gas, let it out slowly at first, etc). After an hour of us being very frusrated, I went out alone and taught myself.
I later taught two friends, explaining the clutch's catch point, and they were 'getting it' within a couple of minutes. A few accidental stalls, sure, but they understood why. 20 minutes or so and they were legitimately ready to drive on the road (both had been driving automatics for years).
My dad had already been driving for 40 years, he totally forgot the catch point even exists.
In my experience I'm not so sure about that. I've meet (and worked with!) bad programmers very much my senior. After working with them I know why they are bad - they don't learn. Even with asking tons of questions and having their work critiqued constructively. I don't know why this is but I've observed it a few times. It seems some small subset of people, no matter how much they do something just don't get better at it. They spend 20-30 years writing software like an amateur who just learning. Someone I know said about this - "experience isn't a measure of time spent doing something."
So, the only real weakness I've found is when someone considers themselves to be done learning. At that point, they are basically done being a "programmer".
I powered through that and ended up doing very well in my CS program at Northwestern, and now am a professional software developer that my peers consider to be a 'rockstar' programmer, although I still contend that I am mediocre and there is always SO much more to learn. At my job I frequently mentor our college interns, and many of them when they come into the job would be laughed out of the room by 'good' programmers, but after a little bit of mentoring and consistent daily practice on the job, in 2 months they emerge 'rockstar' programmers themselves, and in reality they are still probably about average.
Most of the 'bad' programmers many of us come into contact with are just farther behind on their journey to being great software developers, and may only be as bad as they are because of fear to ask questions and be judged by those who think there are only 2 types of programmers.