There are some pieces of code I can implement just as well whether I’m motivated or not (whether I’m sharp or not). I think knowing the personal difference between what I can do while motivated and what I can do otherwise is the real key to consistent productivity. I try and mentally break down my to-do lists into those categories, so that when I’m feeling less sharp I can just fall back into a cache of problems that I know I can solve well even given a temporary decrease in ability.
Somewhat agreed, with the caveat that there is code I can implement when not sharp, which, when I am sharp, I realize why I shouldn’t implement it and use a more elegant approach. This makes it important to set up the to-do lists you mention during sharp time.
I find that I’m occasionally in a mood where I am very sharp but very lazy. That’s the time I use to do most of my planning. Thinking out the high level form of code is almost always fun.
There are some pieces of code I can implement just as well whether I’m motivated or not (whether I’m sharp or not). I think knowing the personal difference between what I can do while motivated and what I can do otherwise is the real key to consistent productivity. I try and mentally break down my to-do lists into those categories, so that when I’m feeling less sharp I can just fall back into a cache of problems that I know I can solve well even given a temporary decrease in ability.
Somewhat agreed, with the caveat that there is code I can implement when not sharp, which, when I am sharp, I realize why I shouldn’t implement it and use a more elegant approach. This makes it important to set up the to-do lists you mention during sharp time.
Agreed.
I find that I’m occasionally in a mood where I am very sharp but very lazy. That’s the time I use to do most of my planning. Thinking out the high level form of code is almost always fun.