b3126044e8
- 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>
37 lines
2.2 KiB
Markdown
37 lines
2.2 KiB
Markdown
---
|
|
aliases: ["Learning"]
|
|
Is A: Responsibility
|
|
Belongs to: "[[area-learning]]"
|
|
Has Measures: ["[[measure-books-per-month]]", "[[measure-evergreen-notes-created]]"]
|
|
Has Procedures: ["[[procedure-weekly-reading-session]]", "[[procedure-evergreen-note-writing]]"]
|
|
Status: Open
|
|
---
|
|
# Learning
|
|
|
|
Learning is the raw material supply chain for everything Refactoring produces. Reading widely, studying deeply, and synthesizing ideas into evergreen notes ensures that the newsletter and podcast draw from a genuine well of insight rather than recycled surface-level takes. This responsibility covers deliberate reading habits, note-taking systems, and the ongoing effort to turn consumption into durable knowledge.
|
|
|
|
## Scope
|
|
|
|
- Maintaining a consistent weekly reading practice across books, articles, and research papers
|
|
- Focusing reading on non-fiction domains: business strategy, technology, behavioral science, and self-improvement
|
|
- Writing evergreen notes that distill key ideas into reusable, linkable knowledge assets
|
|
- Curating a reading pipeline that balances current interests with deliberate exploration of new fields
|
|
- Connecting reading insights to content production — feeding ideas into newsletter essays and podcast topics
|
|
- Reviewing and refining the personal knowledge management workflow periodically
|
|
|
|
## Current state
|
|
|
|
The reading habit is consistent, averaging two or more books per month, with a good mix of business, technology, and science titles. Evergreen note output is meeting the target of three or more per month, though the quality and depth of notes varies — some are thorough syntheses, others are closer to quick highlights that need revisiting.
|
|
|
|
The main gap is in the connection between reading and production. Many good ideas from books end up buried in notes without surfacing in newsletter content or podcast conversations. Building a better bridge between [[procedure-evergreen-note-writing]] and [[procedure-monthly-pillar-planning]] would help close this loop and make the learning investment pay off more directly.
|
|
|
|
## Key procedures
|
|
|
|
- [[procedure-weekly-reading-session]]
|
|
- [[procedure-evergreen-note-writing]]
|
|
|
|
## Key measures
|
|
|
|
- [[measure-books-per-month]]
|
|
- [[measure-evergreen-notes-created]]
|