3 ms·
Is there a reason why you recommend 1-3 hours and not let's say 6-8 hours (split wisely)?
by freshfey 15y ago
Is there a reason why you recommend 1-3 hours and not let's say 6-8 hours (split wisely)?
- viscanti 15y agoIt really depends on the person. I find I'm not able to absorb more than 1-3 hours of new stuff each day. It's also a lot easier for me to commit 1-3 hours every day. There's an idea that you need to learn a lot up front, and then you're a "programmer". Doing 1-3 hours of learning a day, gets you in the habit of ALWAYS learning. You never know enough, so it's not a 3-4 month process where you come out at the other end and you're done. I think 1-3 hours a day is manageable by everyone, and you don't ever run into diminishing returns for the day. That doesn't apply to actually programming. If you're building something, and you have the time, more hours in the day is generally better. If the focus is on learning, 1-3 hours is probably good for most people, and something that's easy to keep up with for years.
- Homunculiheaded 15y agoBecause your goal is to get to thousands of hours of practice. I think the probability of burnout is way too high if you put 6-8 hours of practice in a day. The only way to get to thousands of hours is to practice every day for a long period of time. With 6-8 hours it's very easy to say to your self "Well I did put in all the time yesterday, so today I'll take a break", and this in turn tends to lead to finding yourself spending weeks/months without practice. Slow and steady and whatnot ;)