In Hacker Monthly, Issue 21 Feb 2012 p34:

Being a Great Coder

Do yourself a favor and lose the "great coder" meme. Or get a job at Google and remain blissfully unaware.

One of the best books I've ever read about programming is called "Practicing: A Musicians's Return to Music," were the author talks about his development as a musician. He would receive compliments on how great he was at playing the guitar. At one point he replies, "How would you know?" The better he got, the worse he knew he was.

Your opinion of how great you are at programming will follow a bell curve. You'll start off coming out of college thinking you're ok, memorize a few algorithms and order theory ("the Google disease") and think you're "great" ("Google only hires great coders"). But as you learn more you'll discover that you have SO much more to learn, and as you work on larger projects you'll discover the musician's insight. People would rate you "great,' but you'll be able to say, "How would you know?" At which point, the better you get, the worse you'll know you are.

Anybody who rates themselves as "great" is probably on the uphill side of the learning curve.

If you're trying to learn Clojure, moving into areas that are beyond your comfort zone, and trying to learn literate programming to improve your game, all points to the fact that you will likely reach a point where you feel that being labeled "great" is a sign that the speaker is clueless. Give it 10000 hours.