correlr/roam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

notes

Browse source
This commit is contained in:
Correl Roush 2020-07-19 20:43:28 -04:00
parent ef90126b55
commit 6be8865895
1 changed files with 33 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
20200716231656-how_to_take_smart_notes.org
View file

@ -47,3 +47,36 @@ notes will be what explains them to you again later on. Link them together in
broader topics that serve as an index to a variety of thoughts and ideas. These
notes can later be referenced when building up a full piece. In all likelyhood,
they won't be copied straight in, but instead built upon further.
* Chapter 5: Simplicity Is Paramount
The goal is to build a slip-box thats value only grows the more that is added to
it. This requires the notes that are added permanently to be sufficiently well
written to be understood later, and also to be found when needed. Doctor Ahrens
describes three separate types of notes at play: fleeting notes, project notes,
and permanent notes.
Fleeting notes are not meant to be the slip-box, or at least not for long.
Theyr'e meant as quick snippets captured while doing something else. They're
intended to be taken with minimal interruption, and revisited within the day or
so while they're fresh to be elucidated upon, and then discarded once notes of
value are generated from them.
Project notes exist for the specific purpose of supporting a particular effort,
and should be clearly delineated from the rest of the notes, while still being a
part of the overall collection. This is done to allow them to be discoverable
while working on the project, but easily filtered when not, and to eventually be
archived off when the project is complete.
Permanent notes are the ones that remain valuable independent of any particular
project. It is these that you'll retain and revisit, and should be clearly
written with enough context to be understandable on their own.
Fleeting entries lack substance or context and clutter the collection.
Project-specific notes hold little relevance beyond the project itself, in
content and in timeliness. They should be regularly pruned and archived to keep
the experience of the slip-box frustration-free. To reiterate an idea from
earlier chapters, the ideas is to keep the experience pleasant, and avoid losing
trust in the quality and usefulness of the tool. By remaining diligent about
what goes into the slip-box and what stays, you can avoid falling into the trap
of large repeated clean-ups and other chores.