Deliberate and fully conscious procrastination. Distract yourself deliberately every few hours. Do something completely different in your free time and when procrastinating.

Also, take your time, think things through.

When debugging obvious typos and "impossible" causalities that you still not see after reparsing the code the tenths time - calm down, procrastinate a bit, and restart debugging - discarding assumptions and result from the previous tries.

Completely different can be problematic

@AvatarOfKaine In my experience, the less similarity to the thing you actually tried to do, the better. It can happen that i don't get back to the actual work on the same day - but that is a risk i am willing to take...

@Oktokolo problematic is there is a limitation that resources can put on a person of everything else insanely remains the same

@AvatarOfKaine Just use some of the resources you would otherwise spend on futily rereading the code a tenth time when hunting a bug.

Procrastination is a tool to make your brain dump some cached state so it recalculates that state from fresh observations next time you look at the code. It helps a lot with bug invisibility where you see the code you thought you write instead of the code you actually wrote. It also aids a lot when changing perspective.

Only catch is: You need something that is interesting enough to draw your full attention. And you need to be able to let go of a problem. Some people have problems with the latter and/or lack any hobbies. For them, this strategy just doesn't work as it doesn't lead to the old state being dumped in favor of new state.

Yo congrats on passing 10k

@kiki Thanks - need all the ups i can get for premium.

". Distract yourself deliberately every few hours. Do something completely different in your free time and when procrastinating."

Like you're doing right now?