Progressive Summarization
Table of Contents
- 1. Progressive Summarization
- 1.1. https://fortelabs.co/blog/progressive-summarization-a-practical-technique-for-designing-discoverable-notes/
- 1.2. Designing Discoverable Notes
- 1.3. Is Progressive Summarization a Waste of Time? | JamesStuber.com
- 1.4. Progressive Summarization in org mode
- 1.5. Progressive Summarization jethro
- 1.6. Contrast with How to Take Smart Notes
1. Progressive Summarization
1.1. https://fortelabs.co/blog/progressive-summarization-a-practical-technique-for-designing-discoverable-notes/
1.1.1. It’s easy to transfer content from place to place, but it’s difficult to transform it through time
- It’s difficult to stick to a habit, but you’re just reading that book at the wrong time
- The books that you read today will be useful years later
1.1.2. The challenge it’s not to adquire knowledge, it’s knowing which knowledge is worth adquiring
- We have a lot of content, so access to it is no longer a constraint
1.1.3. Note-fisrt Knowledge Management
Make the design or individual notes the primary factor, not tags or notebooks
1.2. Designing Discoverable Notes
1.3. Is Progressive Summarization a Waste of Time? | JamesStuber.com
all of the above critiques: they entirely miss the point of Progressive Summarization.
Progressive Summarization is not a tool for improving memory, and it is not a tool for thinking.
PS is a tool for reducing waste. It’s a tool for collecting, filtering, surfacing and resurfacing the best ideas with as little effort as possible.
1.3.1. How does PS save time?
With PS, you don’t waste time processing low-value ideas. PS’s principle of opportunistic compression means you only touch a note when it’s relevant to a project you’re working on. In this way, PS creates discoverable and understandable notes with the minimum effort possible, just when you need them.
Second, each time you re-use a note it saves you time and gets more useful. Because the note is progressively summarized, you can get to the right level of context quickly. And while you’re there, might as well make a small improvement for next time.
1.4. Progressive Summarization in org mode
https://www.ianjones.us/progressive-summarization-in-org-mode
https://www.gonsie.com/blorg/org-highlight.html -> Doesn’t work with alist
https://www.mail-archive.com/emacs-orgmode@gnu.org/msg130968.html FINALLY!
1.4.1. Highlight and bold
The complicated thing is using double emphasis at the beggining/end:
bold starts ends
starts ends
Use equal inside bold
code starts !ends!
!starts! ends
https://emacs.stackexchange.com/questions/5889/how-to-highlight-text-permanently-in-org-mode
1.5. Progressive Summarization jethro
https://braindump.jethro.dev/posts/progressive_summarization/
- Layer 1
- When you encounter something interesting, capture it
- When you encounter something interesting, capture it
- Layer 2
- Bold the most interesting parts
- Bold the most interesting parts
- Layer 3
- Highlight the most interesting bolded sections
- Highlight the most interesting bolded sections
- Layer 4
- Summarize the bolded portions and the note in your own words
- Summarize the bolded portions and the note in your own words
- Layer 5
- Turn your notes into something new: a tweet, a blog post, even a book
- Turn your notes into something new: a tweet, a blog post, even a book
1.6. Contrast with How to Take Smart Notes
Seems like a previous step to actually generating a note from it?
It is not as detailed as Smart Notes since the output is not as thorough as academia work