Skip to content

Comment on Keep a programming journalparent

Comments

The OP is keeping a journal, so he has developed a real practice that works for him. I agree that a few sentences describing what he puts in there would have made this article stronger.

The second image of the journal page seems to show a list of possible approaches to a problem. The fourth image looks as if it has performance data and evaluation of a working system, so that is a couple of ideas. I think it is quite a brave thing to post the actual images. Perhaps fortunate the OP does not record team dynamics in his journal.

I work as a teacher, and I use a cheap page a day diary to record a few key points from each lesson. The 'readymade' aspect of the page a day diary seems to reduce the 'threshold' for making notes.

It usually goes:

* Write a todo. Ex: Log errors from Fb. * Ask a question if I'm stuck. Ex: Will Log4R block the reactor? * Play with various approaches. Ex: Write in thread, plug into Goliath's logger. * Note any bugs. Ex: Logger blah blah * Rinse and repeat.

I know its a silly example, but you get the idea. Hope that helps.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.