- I want to share my progress on a task.
- I want people to give me input on the decisions I'm making.
- I want to easily pause a task and come back to it later.
- I want all the rubber ducks.
I initially started doing this solely for the third benefit of being able to easily pause and resume tasks. I basically wanted a coding journal , and it was only a matter of convenience that I used GitHub issues over some random file on my computer.
Eventually, after several ever-so-slightly-awkward conversations where someone thanked me for talking to myself, I realized I'd stumbled on a pretty sweet communication tool. Since communication is generally hard, I was pumped to grow my tool-belt.
I've kept up the monologues ever since I started, and now at Khan Academy it nearly always comes up in my project retrospectives as being super useful . It's definitely a vital part of my workflow now.
I'm suspicious that my comments are slowly getting spammier (a recent one: "Hmm, I think I'll go get a sandwich and then try this again"), but so far nobody has minded :).
|||A blog post written awhile ago talks about how useful coding journals generally are.|
|||At Khan Academy, after every project (which are always 2-4 weeks), everyone involved meets to give feedback to each other and discuss how things went.|
|||Duck image is from wikimedia. See there for licensing and author information.|