Files
tolaria/demo-vault-v2/procedure-weekly-reading-session.md
Test b3126044e8 refactor: flatten vault structure — simplify migration API and flatten demo vault
- Simplify flatten_vault API to return usize instead of MigrationResult struct
- Add KEEP_FOLDERS: attachments/ and _themes/ alongside type/, config/, theme/
- Use HashSet for collision tracking in unique_filename
- Update wikilinks from path-based [[folder/slug]] to title-based [[slug]]
- Clean up empty directories after flattening
- Flatten demo-vault-v2: move all notes from type-based subfolders to root
- Update smoke tests for flat vault structure
- Remove migrate_to_flat_vault from repair_vault (one-time migration only)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-15 23:40:47 +01:00

2.9 KiB

aliases, Is A, Belongs to, Cadence, Owner
aliases Is A Belongs to Cadence Owner
Weekly Reading Session
Procedure responsibility-learning Weekly person-luca-rossi

Weekly Reading Session

Sunday morning reading is the anchor habit for responsibility-learning. Two to three hours of focused, uninterrupted reading creates the raw material that feeds evergreen notes, newsletter essays, and original thinking. Without dedicated reading time, the content pipeline slowly starves — you end up recycling old ideas instead of generating new ones. This is not leisure reading; it is a professional investment in the quality of everything you write and think. The output directly supports measure-books-per-month and fuels the procedure-evergreen-note-writing practice.

Steps

  • Saturday evening: select the book or long-form material for tomorrow's session — have a backup ready in case you finish or lose interest
  • Sunday morning: set up the reading environment — no phone (or phone in another room), coffee prepared, comfortable seating, notebook or highlighter within reach
  • Read for 2-3 hours with full attention — no multitasking, no "quick checks" of email or messages
  • While reading, highlight or mark passages that provoke a reaction: surprise, disagreement, connection to another idea, or a new framing of something familiar
  • After the reading session, spend 15-20 minutes reviewing highlights and writing brief margin notes or annotations that capture your reaction (not just the author's words)
  • Identify 1-2 ideas from the session that are candidates for procedure-evergreen-note-writing this week
  • Update the reading log: book title, pages/chapters completed, and the session's date — this feeds into measure-books-per-month tracking
  • If you finished a book, write a brief (3-5 sentence) personal take: what was the core insight, what did you disagree with, and who should read it

Notes

  • Protect this time ruthlessly. The moment reading sessions become "optional" or "if I have time," they stop happening. Block it on the calendar like any other non-negotiable commitment.
  • Read broadly, not just in your domain. The most valuable newsletter insights come from connecting ideas across fields — a cycling training concept applied to business, or a financial principle applied to content strategy.
  • Alternate between challenging books and enjoyable ones. A steady diet of only difficult material leads to avoidance, while only reading easy material limits growth. The rhythm matters.
  • Physical books and e-ink readers work better than tablets for focused reading. Backlit screens invite distraction and fatigue faster.
  • Do not pressure yourself to finish every book. If a book is not delivering value after 50-75 pages, abandon it without guilt and move to the next one. Life is too short for bad books, and the sunk cost fallacy applies to reading too.