In the context of such a short post, the fact the author mentions going for "a run" twice doesn't seem trivial to me.
Going for "a run" has become such an integral part of "work" for me (software eng), I consider my career choices one of the main factors in my subsequently becoming a distance runner.
I began my foray into software development almost 5 years ago, and in the last 2 - not unconnectedly also my first 2 years working 100% remotely - I've run 2 half marathons (officially, several more in training), a marathon relay, a 10k, and just a couple of weeks ago my first marathon.
Bragging about this because with all the time spent training I developed an even deeper connection between the "work" (solving whatever current problem for my job) and the time I spend running. At this point I often deliberately wait to go for the run until I've really got my mind around the code/feature/bug I'm working on. Once I'm actually moving, I don't really try and actively think about it, but more often than not at some point on my run something will click, and I'll return to my desk with a clearer path forward.