Thinking about it in the current context, I might say that there is something like a prodictivity counter-culture? For example Deep Work seems to value high-poductivity focus on one hand, but being lazy and completely switching off workis lauded as well.
Last thing it reminds me of, is the Mythical Man Month, with its warnings about how adding more people to a project makes it makes it even more behind the schedule.
But even here, I still live with the undrlying assumption that you as a person want to keep producing interesting/important/useful/profitable things. Just that slowing down can get you further.
I have experienced this with myself when working on my masters thesis. I remember that for three months I was just thinking about it. Not really working on anything. And after the idea slowly over the months crystalized as the "right thing to do" I solved a problem in a way that replaced 3Kloc C++ code with 50 lines of Python over a weekend. Then I spent rest of the time running experiments and writing the text :-)
And sometimes I miss this, especially in current agile environment, where sprint retrospective is always around the corner, I don´t feel like I have time to just think about stuff anymore.
Ritch Hickie talk Hammock-driven development seems to be about simmilar concept as well https://github.com/matthiasn/talk-transcripts/blob/master/Hi...
Last thing it reminds me of, is the Mythical Man Month, with its warnings about how adding more people to a project makes it makes it even more behind the schedule.
But even here, I still live with the undrlying assumption that you as a person want to keep producing interesting/important/useful/profitable things. Just that slowing down can get you further.
I have experienced this with myself when working on my masters thesis. I remember that for three months I was just thinking about it. Not really working on anything. And after the idea slowly over the months crystalized as the "right thing to do" I solved a problem in a way that replaced 3Kloc C++ code with 50 lines of Python over a weekend. Then I spent rest of the time running experiments and writing the text :-)
And sometimes I miss this, especially in current agile environment, where sprint retrospective is always around the corner, I don´t feel like I have time to just think about stuff anymore.