It’s never chugging along at a consistent marathon pace. It’s always a series of sprints.
Of course, there are always five other things you know that need to get done besides the problem in front of you, but it can be a challenge to find the correct level of engagement, versus just sitting and 'marinating' in the problem in front of you.
I think the paradox is that if I spend all day doing nothing but reading documentation and farting around on Hacker News, nobody really notices. Not in the same way they notice if I spend a day on 'the wrong thing' (because I know for certain what needs to be done on this other thing). It's seen as wasting resources, because certainly I could have put that energy into the 'right thing'.
The 6 days (not always 6 - maybe more, maybe less) let me come up with and throw out stupid ideas before i've coded them. By the time I come to build something it's a carefully considered thing that'll actually be useful most of the time.
It's not just feature ideas either, it's code design, data design, anything that might be complicated enough that I used to spend multiple days experimenting. It doesn't always work out, but when it doesn't, i've thought it through enough that I have a head start on coming up with a better design.
As someone who has inattentive-subtype ADHD, I must say that this sort of pattern can result in a great deal of loneliness. It is far better to watch the course "learning how to learn" and use something like the Pomodoro technique to explicitly decide whether to be in
- focused mode
- exploratory mode
- actually relaxing and paying attention to your relationships mode
Essentially, what is your 'reward model'? -- https://www.youtube.com/watch?v=PYylPRX6z4Q
Test-Driven-Development is one example of this.
My sprint is not now, my sprint starts later.
The sprint toward my spirit starts now. Reading this comment, reflecting this thought. And another is below.
Upvote the comments that you can relate to and see what bubbles up