3 ms·

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 co

by philtar 13y ago

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

ZirconCode 13y ago
Sure you can. Answer a hard stackoverflow question in your favorite field, Voila, you learn something, or need to connect the dots.
klibertp 13y ago
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 :)
- 212 13y ago
  212
lostlogin 13y ago
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.

by philtar 13y ago

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

ZirconCode 13y ago

Sure you can. Answer a hard stackoverflow question in your favorite field, Voila, you learn something, or need to connect the dots.

klibertp 13y ago

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 :)

212 13y ago
212

lostlogin 13y ago

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.