From: Jeff Schwab <jeff@...>
Date: 2009-03-12T09:23:00+09:00
Subject: Re: How Many hours in A day

Phlip wrote:
> Zayd Connor wrote:
>> I have a very simple ? How many hours in a day should someone who is new
>> to ruby or programming spend learning and coding without over kill.

I'm not a ruby expert, but programming is a lifelong endeavor.  There is 
no amount of time you can spend, beyond which your task will be "done." 
  The more time you spend -- really, the more actual problem-solving you 
do on your own -- the better you'll get.

> On your own, unpaid, you should cram for days.

9-5 developers are universally incompetent.  People who don't code for 
fun never get to explore new design styles, nor cutting-edge 
technologies.  Coding after work is great, specifically because you're 
allowed to fail.

> Behave like videogame 
> addicts, with adult diapers, stacks of canned food next to you, etc. The 
> point is to burn the techniques into your brain.

That's a good way to burn out.

> On the job, work 8 hours a day, go home, and don't program. You owe it 
> to your velocity to keep fresh for your job!

... says someone who frequently posts code on Usenet. :)  Seriously, a 
little after-work coding serves as a mental palate-cleanser; a sort of 
aperitif for the mind.  For me, it's an important part of keeping fresh. 
  YMMV.