4 ms·

I always find writing out my programs (even in pseudocode) before actually attempting to type it out has helped me weed out bugs in the long run. This is especi

I always find writing out my programs (even in pseudocode) before actually attempting to type it out has helped me weed out bugs in the long run. This is especially true as long as whiteboard interviews is still relevant. Despite me typing pretty fast on a keyboard (~90wpm), writing things out on paper makes me think more carefully, and I don't have to maintain a contextual overhead in pressing the right keys or seeing a red, strong underline for every typo I make. This is also true for non programming related work. It frees my mind into solving the actual thing where typing is just the medium. Then again, I grew up doing a lot of writing and only got my first iPhone in college. This might be different for kids who interact with iPads in elementary school though.

brootstrap 9y ago
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.