"What kind of pace are you setting yourself?" I am working "flat out", but it doesn't really feel like "work", though some proofs are taking longer than I'd li

"What kind of pace are you setting yourself?" I am working "flat out", but it doesn't really feel like "work", though some proofs are taking longer than I'd like. More like when started to program when I was about 10 years old and didn't have to worry about things like making a living and so on. I guess this is what working for a ycombinator startup feels like minus the revenue related stresses. "I'm testing the tip I heard somewhere that instead of doing huge chunks and then forget about your goals for a while, it's better to do a bit every day." Even better might be to work a lot every day and not break off. I once asked a (top notch) musician about whether it was better to practice only a little every day, or "woodshed" in huge chunks, he replied the best way was to have both quantity and quality, but if that is not possible have high quality and regularity, rather than a huge effort followed by a vaccum. I suspect that might be advisable to programming skill upgrades as well. So yes I am "working" 10-12 hours a day, but I am not forcing myself to do anything and don't feel stressed. It is just that without the "distraction" of consulting etc, I am able to work uninterruptedly. I keep the guitar nearby, to play an etude or noodle around when I need a break.I also work out every day. I suspect this is not a sustainable (over years, say) pace, but so far so good. we'll see how it evolves.