As goes writing, so goes coding
Writing and structuring can be highly pleasant tasks. But switching from writing to structuring and formatting is like jumping between your favorite song and your favorite movie every few seconds. You ruin both. The more we enjoy doing one thing, the harder it is to abruptly shift to something else, even if we normally enjoy it, too.
Separate the tactical stuff like new functionality, tests, design, refactors, etc. from the strategic stuff like design, research, brainstorming. Decide if you should remove some of that code (you just paid a few bucks to generate) in the first place.
I keep hearing writers going on about enjoying sentences as standalone objects.
A well-known writer got collared by a university student who asked, “Do you think I could be a writer?”
“Well,” the writer said, “I don’t know. . . . Do you like sentences?”
We are largely past this for coding, for better or worse. But, there is still the holistic appreciation of how a program solves its problem space. Whether a human typed it or not, there’s something to a program that concisely composes levers and concepts out of language primitives and then uses them to solve many problems or one problem in-depth.