4 ms·
And so maybe true effectiveness would be achieved by having a torrent of work once a week instead of a few minutes a day.
by dheera 5y ago
And so maybe true effectiveness would be achieved by having a torrent of work once a week instead of a few minutes a day.
- dj_mc_merlin 5y agoBoth. I am naturally a very "torrent of work" kind of person, but I've learned that one approach isn't enough. Some problems require a bit every day, some torrents.
- hutzlibu 5y agoAlso the torrent maybe only comes, if prepared through little drops here and there.
- dreamer7 5y agoI think it depends on the activity. It's impossible to build any medium to high complexity software by working on it for 5 mins a day. But you can make a lot of progress by practising every day for very little time. For example, I've improved on my tucked planche progression by just leaning forward while holding a plank for 5 seconds every day.
- dheera 5y agoYeah I agree. For software I find the major infrastructure laying and overhauling should be done in "torrent" blocks of several hours to a full day, while incremental bugfixes and feature add-ons can be done by daily short amounts of time.
- munificent 5y ago> It's impossible to build any medium to high complexity software by working on it for 5 mins a day. Both of the books I wrote, one of which includes two complete implementations of a programming language, were mostly written in sessions of less than an hour. Occassionally I get longer ones and very often they are much shorter. Learning to task switch and suspend efficiently is also a really valuable skill that improves with practice. I have kids, so if I couldn't make progress while being interrupted, I'd never be able to do anything.
- TeMPOraL 5y agoDo you count only writing time, or also the time you spent constructing the book and associated programs in your head?
- munificent 5y agoAll of it.
- TeMPOraL 5y agoThat's very impressive. I envy you. And I wonder how you do it. How are you able to suspend and resume work on a complex project like this? How are you able to stop thinking about it when scheduled time is up, and then pick it up the next day, without paying a huge time cost of loading yesterday's state back into your head? Could you elaborate on this? I'm asking seriously - I myself wish I could do that. The way I work today, in irregular but long bursts of high focus, is somewhat effective, but doesn't lend itself to having a balance in life (work-life balance, but also "personal interests - life balance").
- thorum 5y agoMy experience has been that a small amount of work each day builds mental momentum which can snowball into something bigger when my schedule opens up and I have some free time & an idea that excites me.
- GeorgeTirebiter 5y agoYes, working on a problem daily means your subconscious is daily prodded to "think about the problem". As you do other things, your brain is 'working on it' so when you do get those few minutes or maybe an hour to work on it, you almost always know what to do - you've been thinking about it all day! There is an apocryphal story of what Newton said when he was asked, "How did you come up with the theory of gravity?" replying: "By thinking about it all the time."
- macksd 5y agoI think at this point we're reading too much into specific units to compare very distinct things. The point of the analogy either way is the compounding effect of seemingly small things repeated.
- binarysolo 5y agoRight, even a day or suncycle is kinda arbitrary and human-scale. Point is just that consistent repeatable practice rewards compoundingly over time.
- fladrif 5y agoto follow the example closer, you need to put in work every day, however small (continuous river flow), and that will carve the channels in your life (eh?) to enable the torrent of work that might come when conditions allow.
- Aeolun 5y agoI think the problem with humans is that, other than with falling rain, the throughput is limited. So you cannot really do a torrent of work on grand canyon scale.