1/ There are two broad approaches to deal with 'information overwhelm':
1. Manage the flow (but still consume it all!) - use shortcuts, tools & tricks, and triaged prioritisation 2. Close the tap - stop the information coming in at the source.
I think #2 is more critical.
2/ I've realised the need to improve my filters & make peace with the fact I won't get to it all.
You don't need to listen to every podcast/read every newsletter (esp. if you're trying to appear smart!) Attention is too precious to not enjoy the process of engaging with content.
3/ My goal is to have 2 lists: 'read' & 'don't read'.
There are thousands of non-fiction books out there, and everyone is convinced that the current book on their nightstand is a 'must-read'.
Whilst I take note of these recommendations, there is only so much time in the world.
4/ So many books are just rehashes of the same old information.
There's often significant overlap (esp. in business books!) and creative reframing of ideas.
We also all know the book that could have been a blog post, but then got padded with anecdotes to fill some page quota.
5/ I recently started the exercise of curating my reading recommendations.
There were nearly 100 books there. Assuming an average reading time of 5 hours (complete thumbsuck), that's 500 hours: 3 weeks of continuous reading 😅
6/ What to do with all of this?
Map and filter.
Step 1 - map: what subject areas do I want to read in?
Step 2 - filter: what books do I want to read in those subject areas?
Step 1 is fairly simple, starting with collecting all the blocks tagged [[to/read]] into a single page.
7/ Mapping is basically a categorisation exercise.
I borrowed the top-down structure of my Scratchpad 'MOC' with different branches, and then did some bottom-up re-shuffling to break these into subcategories based on the books in my list.
Simply put:
- Tree books cover a framework of ideas
- Branch books cover one idea
- Narrative books tell a story
9/ Knowing which classification a book is can help you decide if, and how you want to read it.
Good narrative or tree books are well-worth reading.
For branch books however, you can skim-read (or read a summary) to get the core ideas, or at least be far more selective...
10/ i.e. read only books that you come highly recommended from multiple people.
Now that all my books are arranged in categories (branches😉) and tagged with #narrative or #tree where appropriate, the next step is to curate reviews and figure out which books don't make the cut.
11/ Book summarisation services/good blogs can save you a lot of time with branch books.
I use Shortform for my summaries - their 1-pagers are excellent & have spared me from many laborious reads. Affiliate link 👉🏽shortform.com/onestutteringm… (blas.com is a great blog)
12/ This is what my reading list for writing looks like.
I'm prioritising reading 'On Writing Well' even though there is a Shortform summary. I've heard many good things and it sounds like a great book to get immersed in.
13/ As for Stephen King's memoir, I'll keep that back pocket.
There's also a Shortform summary for that, but autobiographies / biographies have a lot of nuance that are inevitably missed in summaries.
The other two go will be preserved on my 'don't read' list.
14/ Another benefit was the simple pleasure in finally cleaning my [[to/read]] page, which cleared some psychic drag I wasn't even aware of.
There's still a lot more work required, but ultimately I think the pay-off in time saved is well worth the effort 🙂
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ A lot has been said about @tana_inc in the last week.
I've been playing around with it for a few days, and the hype is not unfounded.
I scratched together my first impressions & comparisons, along with musings from older tweets on what this means for knowledge work in teams.
2/ First, a word on sticking with your current tool.
There's a lot to be gained from doubling down on one tool, but there's no harm in play 😉 I'm already seeing benefits cross-pollinating into Logseq - the tools complement each other well.
3/ Let's start with problems rather than tools, as software exists to solve user challenges.
PKM users require frictionless input, organisation & retrieval of information to gain mental clarity, generate original output or improve outcomes in their field
33 thoughts to commemorate another trip around the sun.
These are some things I've been chewing on over the last while, and I thought it would be a good marker to remember the year by.
The statements are completely unsubstantiated, so take with a pinch (handful) of salt.
As always, I feel the need to caveat.
Any effort to capture broad perspectives in pithy tweets is invariably going to miss some marks. Hopefully there's sufficient ambiguity and minimal preachiness.
Where I fall short, remember your handful of salt 🙏🏽
1. Universal statements on the best way to live your life are best avoided.
Everything is contextual. The current moment is not a snapshot in time, but rather the downstream consequence of innumerable circumstances, and everyone's path to this moment is different.
The lazy answer: all the nouns - people, projects, places. But there's far more to it!
I've been thinking about different components of 'corporate' work & putting together a rough list of links that might help structure workflows.
Many knowledge workers will shift to personal (or collective) knowledge graphs & need frameworks for organising their information.
There are existing frameworks (e.g. the RDF, see wikidata.org/wiki/Wikidata:…) which can be leveraged, but everyone will have their own preferences.
You'll know the feeling of wanting to do something your own way if you've ever opened someone else's Excel model or Notion DB.
It will take time to develop & refine approaches that feel intuitive to the individual, but still conform to protocols that allow for interoperability.
1/ I believe that page properties are going to become an ever-increasing part of @logseq workflows and systems in the future (possibly more so than block properties)
Adding properties to pages (and blocks) adds resolution to links by specifying the nature of the relationship.
2/ Have a look at what @zsviczian is doing in Obsidian with TheBrain plugin to make the graph view more powerful.
It's all based on meta-data, which is implemented in Logseq using properties. It's only a matter of time before we see similar functionality in Logseq (I hope!)
3/ However, most people's experience with page properties is this greyed out block.
Depending on when you joined Logseq, you will often find page titles in YAML format when you click into that block. To change this to the new format, delete the dashes and add another colon
These parts are constantly expressing themselves in the beautiful and chaotic dance of life. Over the years, it's natural for dominant parts to take centre stage.
Other parts of you might be suppressed or put away for a rainy day.
2/ Now combine this with our dualism. When we judge others (or ourselves) we often default to binary definitions of 'good' or 'bad'.
Judgements become all-consuming causal loops: 'she is a good person because of x'; 'he is a bad person because he did y'.
One strike, you're out!
3/ A family man of 30 years has a one-night-stand on a business trip...
Does that make him 'bad'? The act itself is bad if it was outside of the marital agreement.
However, I'm sure many can acknowledge the part of themselves that longs for similar forbidden, novel excitement?