I also agree about tracking time. Many studies on expertise suggest that it
takes about 10000 hours of practice to become an expert at most things -
chess, a musical instrument, programming etc. outliers by Malcolm gladwell
has a nice summary of this sort of research.
Sent from my iPhone
On Dec 16, 2012, at 12:25, Camilo Cienfuegos email@example.com
I completely agree with Jake Jenkins. I am using beeminder for a number of
personal projects too.
I think quality time (maybe in terms of high-intensity pomodoros, 25
minutes each) would be great metrics.
In order to get used to the practice of programming, I would commit to
coding just one pomodoro (or 25 minutes) a day the first week.
Then I would raise the bar gradually until the time you have available, or
the moment you feel you find difficult to keep high concentration
P: Why is this Email 5 sentences or less?
From: Jake Jenkins firstname.lastname@example.org
Sent: Sunday, December 16, 2012 6:53 PM
Subject: Re: Practice Programming
I have never tried to learn to code, but i do have some experience using
Beeminder to track “deliberate practice.”
I think I would track quality time spent programming. Sometimes this might
result in one line of code or maybe 20. My basic understanding is that
more isn’t necessarily better.
I think the overall goal should be to keep logging the time, learn and
practice new techniques, challenge yourself with increasingly challenging
Measuring time would work well with the course too, although I would count
time actually coding, not watching lectures or reading tutorials, towards
your overall goal.
On Dec 16, 2012 12:16 PM, “David John Wilson” email@example.com wrote:
Thanks, Brent. Very helpful.