Programming is better if you do 3.5 hours once a week than 30 minutes every day.
I also walk 3 miles, every morning. It helps the old ticker to keep ticking. I used to run, but kept injuring myself, resulting in long breaks.
My resting heart rate (in my 30s) is 48 bpm. Forty-eight! (As measured on multiple occasions by genuine hospital equipment that I happened to be using in the course of testing/working on it.) For someone who used to be a fat guy, that seems incredible. And yet there it is.
Read the parent comment again.
But read what I wrote: “This is not the case for me.”
I won’t speak to programming only 30 minutes a day, or only three and a half hours a week. I don’t do it, and don’t know anyone that does. It’s a strawman argument that doesn’t really apply to any real-world scenario. I simply used it as a fulcrum to make a comment, based on my own, real-world experience. I also used it to mention something that has a bit more relevance to the article, itself.
It applies to my hobby projects at least. Also - if nobody does it then there's a reason for that :)
"Multiple hours every day" was not an option.
Because I can certainly agree that whenever you know what you are doing and have a task that needs to be done hammering it out all at once is much better than splitting it up and doing parts of it each day. Now imagine you have to study for a python test coming up in 2 weeks as an absolute begginer beginner and you have the option of looking at stuff in 30min chunks per day or 3.5 hours per day all at once. Which option would you pick?
Sports https://sportscienceinsider.com/massed-vs-distributed-practi...