Here is something i would say with two shots of tequila:

I have always thought that there are few steps in learning programming:

Step 1: You learn to write basic language constructs and statements.
and then you start - converting your "ideas" into "something that works".

Step 2. You master most of the language feature
and then you start - converting your "advanced ideas" into "something that works".

Step 3. You have mastered most of language features and worked on many "somethings that work".
and then your concern is now on writing better code, more organized code, quality code and efficient code.

The difference between programming and good programming can be subtly illustrated with the quote "a code that works is not always a better code!"

Those geeks programmers have not all of a sudden learnt to write "beautiful flow of code", it took them years of practice and reading on "how to write better code".

Here are few links that will help you get most out of this feeling:
http://samizdat.mines.edu/howto/HowToBeAProgrammer.html
Software development book, written by Steve McConnell http://www.cc2e.com