Sometimes you have some control flow logic you are writing in your programming language of choice and you think you can do it in your mind, but it is just too complicated to leave your fingertips straight away. The mental model is just too much. I end up having to relearn or re-remember that the best way is to just step away. Yesterday I just stepped away from my laptop, went to a coffee shop with my small notebook and pen. Now without the constraints of all the rest of the code code involved, let alone all the random browser windows and tabs I had open at home, focusing on pen and paper, I could map out my control flow logic, thinking simply with my input and outputs, that is, what are parameters that can be adjusted and what are the expected outputs, I could plainly write these out, and then somewhat simple representations of the control flow just started to surface. Yes in the worst case scenario, I may end up summoning a giant bitmap truth table to do the job, but sometimes just pen and paper will do. But anyway these two are both superior to hoping you will simply write a good answer on the first try. 

This is otherwise known as writer's block in the literary world. The best thing is to just write something. A writer of prose can then proceed to switch to their listening/critiquing brain and think of edits. While, after writing out some code, one may switch to their QA/hacking brain, to test out the newly written code, and see how it goes. Then switch back to to writing mode as needed. But as with one of the great writing take-aways I got from Barbara Oakley's Learning How to Learn, one ought to single-track with either the writing brain or the editing brain, but not with both at once. And that's a good approach to tackling or avoiding choice paralysis, 😅.