Interesting, completely different from my teaching and CTO experience. Also interesting it looks very different from German universities, where e.g. in Berlin the majority of students I've interviewed can't do FizzBuzz in an online interview.
How would you assess "good programmer"?
From a very practical point of view, mine would be something like can write a feature on his/her own, gets transactions correct, doesn't create performance bugs that show in live systems, good maintainable, readable, understandable architecture. We definetly could not get everybody on that level even with a lot of mentoring.
We had a CTO meetup recently and mostly everyone shared the same experience.
Coming back, would be interested in "How would you assess good programmer"?
There's things that can make it take longer of course. If you're not familiar with computers at all, or have never even owned a computer in your life of course you will take longer to learn. If you are not an analytical person you will have to train your brain. If you're bad at even basic math you'll have to learn that too. You may have to do more learning than other people to learn to code but you can still do it.
It's more like playing piano, some have the ear for music and some don't (I haven't although I love Mahler ;-) And putting a lot of effort into learning to play piano, many people are not becoming the equivalent of "good engineers".
I'm holding workshops "Coding for managers" to C-level and VCs. I agree with "You don't have to be born a genius or super special to do it", many people are astonished when they write their first code.
Incidently I will give a workshop here inhouse today to non-programmers.