I second the suggestion for DeepWork. The bit on "Embracing Boredom" is a really good way to exercise that muscle. Also, think deeply about the axiom "think mor

I second the suggestion for DeepWork. The bit on "Embracing Boredom" is a really good way to exercise that muscle. Also, think deeply about the axiom "think more, type less." Ideally you're programming to create long-ish term solutions. Programming for the flow or gratification does not lend itself well to that. On the other hand, if you're in competitive programming, think about the gratification you can get by writing clean AND fast code.