Discussion in 'Programming' started by aidancheddar, May 14, 2015.
I disagree with the guy in the Thinking for programmers video claiming you have to write in order to think. You really don't.
But throughout the development process, I've come to learn that it can help to spend upwards of a week or month thinking things over for critical code. Chances are higher that you'll get it almost right the first time around . That way you'll only need minor tweaks later on.
Honestly, I'm thinking of swapping that video with another one. Now that I think about it.
That said, it can be useful to write your thinking down if your code is too large and/or complex to fit in your head. Here's a thread I made when I was overhauling the updater. I knew pretty much what had to be done, but writing it down allowed me to check my own thinking and have others check it for me.
Separate names with a comma.