📎 Webclip
How do you take notes while you code?
The discussion asks how people take notes while writing code, whether they organize them, and what information is worth keeping. The replies focus on notes for current tasks, complex problems, future reference, and shared project context.
Reading notes#
- One person uses Obsidian for to-dos, daily reflection, meeting notes, definitions, and related work, but switches to paper when very stressed.
- Paper is described as useful for dumping thoughts and ideas, and one commenter uses handwritten notes on a reMarkable tablet.
- Adam Davis says he sometimes sketches diagrams on a Wacom tablet and mostly uses a small text document for TODO items on the current ticket.
- When work is particularly complex, he keeps notes for later reference, but usually the ticket, code, and comments already contain enough detail.
- Another commenter edits the original ticket so notes stay available if someone else takes over the work.
- One person uses Jira for notes as subtasks or comments, then returns to the task to check that the change matches it.
- Several replies describe Obsidian as a place for work planning or personal notes without the distraction of designing dashboards, and one commenter says it can lead into personal knowledge management.
- Notion is described as highly customizable, but also as something that can become distracting because of its layout and design options.
- Adam Davis says he uses Notion mainly for blog posts and for scheduling publication dates.
- One commenter uses Slack messages to self for long codebase-specific commands, and Adam suggests a
development.mdfile for quick reference. - Other tools mentioned include org-mode with Git or Perforce, Craft, Apple Notes, Pocket, bullet journals, Goodnotes, and a home scripts folder with shell aliases.
- A recurring point is that the best tool depends on the task, the need to share notes, and whether the notes must stay with the project.
