yeah i think this is a gooid practice rather then diving right into the editor. Of course certain tasks you might know exactly where/what to code so you just get it done. But if there is any uncertainty or open-endedness i find it's very helpful to write out a set of steps to accomplish. breakign down the problem , smaller chunks etc. many benefits for me not limited to better code less bugs. Biggest one for me is the ability to turn off my dang monitor for a while and look at something that is not a screen. I'll grab my notebook, go sit by a window or something and start brainstorming. it's a nice refresh, plus when you get back to your terminal it's moreso a translation exercise and you can really pump out the code fast.