Keeping a Coder's Journal
summary
Promotes keeping a coder’s journal as a practical habit and shows an early digital example from the Netscape era; cites that about 7% of French people keep journals and recommends daily, weekly and monthly reviews. Advises using very quick 30‑second indicators (smiley, checkbox/percentage/scale) to track well‑being, progress and learning, and recording traces such as notes, sketches, tech pros/cons, bug postmortems and decision records. Recommends storing journals on paper or in GitHub with indexed pages and attention to privacy, and tuning format and cadence over time.
AI-written summary · about
chapters (8)
- 0:00Code journal introduction
- 2:27Why keep a journal
- 3:53Define journal needs
- 5:17Trace types to log
- 6:18Daily indicators tracking
- 8:48Visual and technical traces
- 10:34Journal support and setup
- 12:20Fine-tuning the journal
related talks
46mStaying Human While Coding
44mHow do you think when you're coding?
22mNotes to my younger self
42mWhen you think there is no time for learning or coding
26mWhat Happens When You Don't Write the Code — Advice I Wish I'd Taken 10 Years Ago
47mTracking And Hacking Your Career
50mHow I'm Becoming a Programmer
10mExplains 5 Steps to Get Better at Coding