Workflow Suggestions

Listed here are some loose workflow ideas to get you started. They all rely on the same simple idea: attach a note to a path, and let your editor and habits do the rest.

• Project journal:
  • Attach a note the root and use it as a running journal: what you were doing when you stopped, what to do next, etc.
• File-level “why” notes:
  • Add notes to implementation heavy or non-obvious files to capture invariants and assumptions, tradeoffs that aren’t obvious from the code, “don’t forget to refactor XYZ”, etc.
• Low-friction scratchpads:
  • TODOs that aren’t ready for issues
  • dead ends you might want to revisit
• Directory scoped task lists:
  • refactors scoped to that subtree
  • cleanup reminders
  • (avoids one giant project TODO list and keeps tasks in their domain)
• Debugging breadcrumbs
  • attach notes to files where symptoms manifest, what hypotheses you’ve tried, etc.

And finally, don’t forget to use wwid prune periodically! wwid works best with temporary notes that are intentionally disposable. Think of it like a stack, and don’t be afraid to pop notes when you’re done with them!