Joe Wiltrout wrote:
>>> Many of us would still be waiting if we were gonna wait 40 years to make
>>> something.  I'm not even 40 yet.  :)
>> I suppose I should stop writing code.  My forty years haven't passed yet
>> either.
> 
> Hate to break it to you, but that *was* exageration. Yall said varying 
> answers from 5-6 to 10 years. I have friends who learned to program from 
> scratch in 6 months flat. Making games on the Gamebryo Engine and C++, 
> all that good stuff. 

One thing that is lacking here is the fact that programming/coding is
only (or at least *should* only) be about 10-20% of the total time you
spend on any project.  The rest should be planning.  Coding is the easy
part.  Coming up with the proper use cases, Object structures, flow
charts, etc is the hard part.  This is the part that takes literally a
decade or so of experience to learn. (Don't get me wrong, I don't have
this experience, I just see see the people with the experience every day)

In my Principles of Programming Languages class we crash-coursed about a
dozen languages of all types, and after that I've learned to pick up new
languages very quickly.  But that doesn't mean, by any stretch of the
imagination, that I could write good, well written software in any of
them.  I can get by in all of them, but I'm only fluent in a handful.

--
  Travis Warlick

  "Programming in Java is like dealing with your mom --
   it's kind, forgiving, and gently chastising.
   Programming in C++ is like dealing with a disgruntled
   girlfriend -- it's cold, unforgiving, and doesn't tell
   you what you've done wrong."