Of course, it's not magic. My code has still deadlocked.
The mindset that Go enforces, by virtue of checking the types, has led me to try being more careful in my regular work. I now try to make notes on everything that I need to come back to as I'm exploring a problem (such as: "what code interacts with this variable?") so that I can check my plan against all relevant cases. Likewise, a multi-step change will end up with a few bullet points like...
EmailBounce (#3351)This also helps in event of interruptions, such as realizing the office manager's radio is playing the same annoying pop songs again today, for the 110th day in a row. There's a list of stuff to help re-establish concentration, knowing I'm not forgetting anything.
- set in SES bounce processor
- clear when email changes
- react in notifier code
For complex issues and solutions, doing the design on paper has an extra benefit. Paper encourages brevity. There's only so much room within the confines of a page, and it takes a while to write. Consequently, pseudo code tends to stay pseudo code, at an appropriate level of abstraction, when writing out steps. It's the exact opposite of the temptation to switch to writing the real code when trying to write pseudo code in a text editor. It looks like a convenient shortcut to combine the two coding steps, but then the faults in the overall plan don't get noticed until (often) most of the way through—then a random amount of already-written code is made irrelevant or wrong.
Modifying half-implemented approach A to become approach B (hopefully not with the same last-lap change of course) adds a lot of mental state to juggle. Now there are four states complected: original code, usable code from A, unusable but not yet changed code from A, and code from B. It can be quite useful, and a bit simpler, to work out some of those false starts in advance, on paper. Then there's both a record of where my thoughts have been, and a clean body of current code to implement the final result.
As useful as paper can be, there are also times when it's at a disadvantage. For picking apart tricky, complex control flow with nested ifs, repeated conditionals, and the like, I find it easiest to copy the code into a new window and then start deleting lines and replacing them with pseudo-code comments. Often, hundreds of lines can be reduced to a single window, which makes it trivial to get a higher-level overview of what's being accomplished.
Paper's other major disadvantage is that it lacks undo. I've learned by the number of cross-outs on the page just how frequently I rename things as I get a better sense of the problem and what those parts represent in the whole. (I have even been known to choose a name, cross it out in favor of an alternate, then cross out the alternate to restore the original.)
Overall, though, for the appropriate tasks, it's been a great advantage these past few months to put more effort into paper and less into backtracking in vim.