News for hackers. Stuff that matters.
Re:Day 180: Finished by chestnut-tree on Sunday September 29, 2013 @05:00AM (#6464593)
Very inspiring. I think this reinforces the idea that regular practice every day (even if it's short practice) is often better than longer sessions done intermittently or spaced apart more widely (like once a week).

Here's another example of the "daily practice" approach from a different domain. A self-taught designer callled Mike Winkelmann has been posting his "everydays" on his website. From his site's description:

"Originally I started out drawing and did that everyday for a year. Then I decided I'd like to learn a 3D animation package so I did a render using Cinema 4D every day for two years. Then I did some photography and also Adobe Illustrator for a bit..."

http://www.beeple-crap.com/everydays.php

Edit: Just to add, another great post on the idea of practicing everyday from a motion graphics designer. I think it's applicable to any field:

http://greyscalegorilla.com/blog/2013/01/one-a-day/

Re:Day 180: Finished by lmartel on Sunday September 29, 2013 @10:02PM (#6467417)
I agree with you, but keep in mind that Jennifer has mentioned that she spent 8-10 hours per day on this project.
Re:Day 180: Finished by possibilistic on Monday September 30, 2013 @12:04AM (#6467714)
Where did she find the time? Is she a student? Was every one of these projects done on a consecutive day--including weekends? (I'm unfamiliar with this project.)

Regardless, kudos to her--this is a great way to learn.

Re:Day 180: Finished by roninresearcher on Sunday September 29, 2013 @05:03PM (#6466512)
Adding another thread that reinforces regular practice.

http://www.conceptart.org/forums/showthread.php?t=870

Re:Day 180: Finished by philtar on Sunday September 29, 2013 @05:49AM (#6464681)
I don't think short practice does anything for you when it comes to something like coding.

I can't see anyone benefiting from less than a couple of hours of coding

Re:Day 180: Finished by klibertp on Sunday September 29, 2013 @12:01PM (#6465492)
From my own struggle to learn something each day I can tell you that - at least for me - what you said is wrong. There are many "workflows" I tried and am still using, but generally speaking even 15 minutes is enough to gain something valuable. For example, when reading a technical book 15 minutes is enough to read a descriptions of a (sub)problem and to understand high-level concepts used in it's solution (if it's not, you're reading wrong book). I then go to work and think about the details of the solution during the lunch break and commute. Another 15-30 minutes in the evening is enough to check what I thought up with a book and realize where my thinking was incorrect. Then the next day I can code up whatever I was reading about in an hour max, but frequently less (if not, then I was reading wrong book - that is one which I was not prepared to read yet). Then in the next days I can deepen my understanding with 30-45 minutes sessions, and at the end of the week I have the problem internalized and I can move on.

That being said, when I'm not under extreme time constraints, I'm using other approaches. For example, for a whole week I'm reading and gathering bits of information I will need to build something. I have a large file, where I paste links, paragraphs of text from articles and write tiny little snippets of code, either mine or borrowed from somewhere. All this takes an hour or a little more each day (but it's nice that it can be divided into pieces). Then over the weekend I try to make this amorphous mass of data into understanding, in one or a few coding sessions.

There are other ways to make the best use of what little time we get, too. They'd better be, because otherwise we'd be royally screwed as working programmers :)

Re:Day 180: Finished by ZirconCode on Sunday September 29, 2013 @06:38AM (#6464756)
Sure you can. Answer a hard stackoverflow question in your favorite field, Voila, you learn something, or need to connect the dots.
Re:Day 180: Finished by lostlogin on Monday September 30, 2013 @02:56AM (#6468168)
When you have a full time job and a family there is no other option. My progress is slow and painful. By the time I've found my place in documentation/text, found where I was stuck and then searched solution to a problem, I'm lucky if I get a few lines down. I'm miles ahead if where I was, and thousands of miles from where I want to be. If I had several more hours in a day it would be great. I trade sleep for code time occasionally, but if I do it too often health or job suffer.