The basic pattern involves a good kind of task, and a good way to get to it. Both parts are vital.
The task may be to handle a test failure, a documentation omission, the simple kind of bug. Anything that's part chore (to start on it without flow) and part flow (to leave it flowing).
The good approaches involve the editor and do not involve a web
browser. Running a build and having the build tool deliver
compiler error messages is really good. It doesn't matter
whether the messages are from the compiler, from a linter,
a documentation tool or
from a unit test. Anything, so long as it makes the editor open a
plausible file and shows me a reasonable message.
Reading something like the aox notes file has also worked well for me. That puts me in the editor window, less than a second away from the source file that needs work.
My 2¢, mileage may vary.
Milage does vary.
Mileage varies even for me. At the moment I find it very hard to use this technique. All the bugtracking, testing, CI, all that's web-based, and the build tool is so slow that it's difficult to even stay in the flow. Pity. I hoped to find a way by writing this.