The even bigger piece of wisdom I probably need to follow here is in paying attention to my subconscious. I think I'll often feel bad for leaving something untouched or half finished, but coming back and getting space away from things you don't want to do really does give you either time to rejuvenate or clarity on what to do better.
Absolutely, and it's one of the benefits of having years of experience writing software. Sometimes my instincts tell me something is off, even if I can't yet identify exactly what it is. Coming back to the problem later with a fresh perspective can do wonders.
Bill Gates' take on preferring a lazy person for a tough job because they'll find the easiest way to do it? I'm all for efficiency, but maybe "lazy" isn't the word I'd use. Resourceful, perhaps? It's a minor quibble, but it sticks out to me.
The recency effect is a trap I've fallen into more times than I care to admit. Setting tasks aside to gauge their importance later is a tactic I'll have to try more deliberately. And avoiding rework by getting things clear the first time? Absolutely. Nothing more frustrating than going over the same ground because of a misunderstanding.