Currently, I'm sort of split between three tools. Omnifocus (a GTD manager) for tracking all the tasks, quiver for notes through the day, and then I use [emergent task planner], a paper based task planner for the days tasks. As much as omnifocus/gtd helps me track things, I found using paper to block out each hour of the workday ahead of time really helps me focus. If I find myself losing focus, I can refer to that and (usually) get myself back on track.
Ask HN: Do you keep a developer diary?
21–30 of 61 posts
Re: Ask HN: Do you keep a developer diary?
#22Re: Ask HN: Do you keep a developer diary?
#23What finally made it into a working solution is writing plain markdown files, one per day, automatically synced to bitbucket via tiny bash scripts that initiate a new file for the day (aliased to 'j' for minimal hurdle to start writing), opens them in an editor, and committs to the repo after closing the editor.
It is available here: https://github.com/samuell/mdnote
The nice thing with markdown, if you make a level-1 header for each new file, is that you can concatenate the file into a long file, and run pandoc -i allnotes.md -o allnotes.epub, and get a formatted and searchable notebook for offline use, when you want to read it, with the Level-1 headings denoting chapters - so, one chapter per day!
(I have a script for this too of course: https://github.com/samuell/mdnote/blob/master/as_epub.sh).
Re: Ask HN: Do you keep a developer diary?
#24I use Evernote for this - every time I figure out how to do something I drop it in a note. I create 4-5 notes a day. It's incredibly useful - I find myself referring back to some notes months after the fact. My team also do standups on Slack, and I've got into the habit of writing detailed Slack stand up bullet points with links to commits, documents I've created and so on - almost a semi-public developer diary. I do…
Re: Ask HN: Do you keep a developer diary?
#25Share the wealth! :)
Re: Ask HN: Do you keep a developer diary?
#26Initially I kept notes in Evernote, but eventually switched to Quiver (http://happenapps.com/).
Re: Ask HN: Do you keep a developer diary?
#27Something that is yours and walks out the door with you, every day.
When the system or someone starts to screw you, such a record can be useful and actually viewed with some validity. Better yet, can be meeting minutes and internal communications that document the situation.
There's a reason Comey is known for writing memos about problematic situations.
Re: Ask HN: Do you keep a developer diary?
#28What I do keep is a large file of projects or snippets of projects, sometimes with extensive notes.
I refer back to these frequently to see how I did something or look at code samples.
But, as time goes on this has become a bit of maze to wade through. I spend time trying to remember what project it was etc. etc. Grep helps a bit :). It would be better to organize this somehow. Not sure I'm interested in a full blown diary though. DRY.
Re: Ask HN: Do you keep a developer diary?
#29You can create checklists. You can share anything from your mobile with trello so I keep track of everything I read.
Re: Ask HN: Do you keep a developer diary?
#30This creates a feedback loop for stress reduction where I aim to mitigate both the likelihood of having a crisis and train a calm response by learning how to deal with smaller stuff so that the day is full of 1's. I chuck it all in a text file once a day, and return to it because my todo is also in there so I always have a backlog. I don't distinguish between work and hone tasks although I might if I were going in to an office.
Long form diaries I don't really engage with because they'd sap relatively more time - I would get caught in trying to make it a storytelling experience.