Sinds de val van het IJzeren Gordijn zijn de wolven in aantocht. En deze week bereikte een wolf Vathorst. Daarbij werd de wolf op video vastgelegd door een bewakingscamera.

Die wolf is wat mij betreft slechts afleiding in de video, want daar heeft vooralsnog niemand last van en behoeft geen (re)actie.

De video laat echter twee dingen zien die voor het alledaagse leven in een wijk wél van belang zijn.

Ik fiets elke doordeweekse ochtend met onze dochter door deze zelfde straat naar school. Bijna altijd staat er een auto geparkeerd op de t-splitsing in de video. Of de auto die je ziet, of de auto die je in de video op de oprit ziet staan, één van beiden staat altijd in de weg.

De camera die de wolf waarnam neemt daarbij ook elke ochtend ons waar, omdat de camera de gehele openbare weg (en trottoir) opneemt. Ongetwijfeld worden die beelden opgeslagen ergens in een cloud, en zo onze dagelijkse bewegingen (buiten de EU) opgeslagen. Een juist ingestelde camera zou lager gericht moeten zijn, om alleen het eigen terrein vast te leggen.

Een wolf loopt langs aan de overkant van de straat. Problematischer dan de wolf is het feit dat de camera de overkant van de straat vastlegt.

I’ve read something, so then what?

How and when do I turn what I read into notes, for learning, for retention, for use elsewhere? Having at least some system for this I found is crucial to have somewhere to go with the ideas, associations and thoughts that reading non-fiction creates. I know this because how the absence of a system to take note of my reading feels. For an extended time at some point I did not read any non-fiction simply because I had nowhere to go with the material I learned about, no application, no outlet, and the ideas plus the urge to do something with them kept swirling around in my head creating noisy chaos and frustration.

Having some system is key therefore. What I describe below is my current incarnation of a system, it shifts over time, tools come and go, and therefore it is a snapshot. At the same time my general information strategies and personal knowledge management haven’t fundamentally changed in 20 years. The source of any continuity or consistency is me, not my tools. That said, none of what follows is very strict, it is meant to be forgiving. The source of inconsistency is also me, not my tooling. Not much of it is blind routine. Yet it is way more than doing nothing. My notes create a ratcheting effect, not allowing movement backwards, which is very valuable to me.

Inputs to outputs and the role of friction

Previously I described the flows of various reading inputs to my main tool in working with notes, Obsidian (my entire Obsidian set-up I described in Oct 2000), and the few outputs that flow from them. The image below gives an overview (click for larger version).

The specific steps and tools mentioned in the image are of less importance here. Key is the locus and role of friction in the depicted flows. There is friction in getting material, both source texts and my annotations for them, into my note making tool. This friction I seek to reduce, making it easier to get material to the place where I can work with it. Similarly I’ve reduced friction in getting outputs into the world (my blog, client websites, book lists for instance). Where I don’t seek to reduce friction is in working with notes (expect perhaps for functionality like search), because there friction is the actual work, where the thinking, rewriting, rearranging etc is happening. There is no way around friction there, because it is how I add value to my notes, how I learn and remember things.

The rest of this posting focuses mostly on what happens in the middle section, where the work is, between the inputs and outputs: what do I do there with annotations from what I read?

Web articles via browser

I use a markdown clipper in my browser to save web articles directly as markdown in a folder NewClippings that is part of my notes vault in Obsidian. Usually these come from my feedreading (over 400 individual blogs) or clicking links in those blogs. Saving is not a postponement and promise to self to ‘read later’ which never happens. It is the result of a curation decision, an intentional step, after skimming the web article. I skim looking for suprisal, and I jot down specific reasons for saving it with the web article. This way my future self will know why I was interested in the article originally. Those reasons may be a novel insight in the article, associations I make with other notes I have etc.

Two examples:

Reason: good overview of AI algo’s not doing what we think they’re doing. Types of mistakes made in training models. Rich source of examples. Compare to note [[Relevance of ethics for machine learning 20201219142147]].

Reason: Steps by Chinese gov against BATX’s ANT group. I see this in light of geopolitical positioning w.r.t. digital and data (compare to [[Data is a geopolitical factor 20180419080356]] and to [[Euproposition]]). Also see notes in [[Logic Magazine 7 China]]. Read for notes, not notions. Is there a usable contrast with the EU’s proposition?

I currently have some 825 clippings, of which about 150 are my own old blogposts recycling my earlier writings that way. I do not intend to always process them into other more permanent notes, I don’t treat it as an inbox. It is a repository in its own right, that I can search for additional material. I do pick out clipped webpages for processing, if that is logical from what I’m doing at some point in time.
Whenever I do process an article, it means deleting everything that I don’t think is interesting from my point of view, and summarising and paraphrasing the points I do find interesting. At the top, where the original reason for saving an article is, I keep track of the status of that process. The reworked article remains in the same folder as the other saved articles during this process. If I lift specific notes or notions from the article that can stand on their own, those will link to the original web article by url as source, and end up in one of three notes folders (one for conceptual notes, one for actionable ideas, one for more factual notes and examples) where they are woven into the wider collection by linking. Where that lifting is done I delete the original article from the clippings folder.

Scientific Articles and PDFs via Zotero

I use Zotero to keep a library of scientific articles and other PDFs (e.g. European Commission legal documentation). My motivation for saving them is stored as remark with the material in Zotero. When I save something I usually mention it in my Day logs in my notes, so that I can stumble across it again for processing.
I read those PDFs and highlight and comment in the PDF itself.
Until last week’s Zotero update I could easily grab those highlights and notes using a plugin and save them in markdown into my Obsidian notes vault. The update broke the plugin, so that flow is temporarily out of order. Any highlights and annotations in such a markdown file have a link to the corresponding location in the PDF in Zotero, meaning I can directly jump to the source.

Then, like with web articles I summarise, paraphrase and connect to other notes in steps. Notes/notions that stand on their own, contain the links to Zotero sources. I write, link and fill those stand alone notes from within the annotations first. Once I’ve taken out all I want from an article I delete the annotations note, because all created individual notes link to their source in Zotero. Currently some 10% of learning related notes link to a source in Zotero, after two years of using Zotero.

Books via Kindle

I don’t nearly read the amount of non-fiction I’d like. So none of this is ‘routine’ but it is what has emerged so far as workflow.

When I start reading a non-fiction book, I create a note that serves as the place for thinking and processing what I read. I prefill that note with a template that contains some datafields for my book lists and provide a structure of questions to explore the book before reading. What do I think it is about, what seems the author’s purpose with this book, why am I interested in reading it, what kind of surprisal am I after? What do the different chapters discuss, which ones seem most interesting to me and why? This all before I start reading parts of the book.

While I’m reading I follow two ways of making notes:

  • I make notes alongside reading the book, and put them in the note I created for the book. These are descriptions and summaries of key ideas, but also associations and links to other things, questions that arise while reading. Basically my half of being in dialogue with the book. This is what I’ve done exlusively until recently.
  • Recently I started using the Kindle sync plugin for Obsidian, which grabs all my Kindle highlights and annotations and puts them in a markdown note in my Obsidian vault, including links to the right paragraph in the book. I link that note with annotations to the note I made about the book. I never was a big highlighter / annotator in my e-books because of the difficulty of doing anything with it, but thanks to this plugin removing the barriers I started annotating and highlighting much more intensively.

In the book note that I created before reading I then work through the things I highlighted and annotated. Thinking about connections, contrasts etc, and linking to existing notes accordingly. It is also where I start paraphrasing and writing snippets that can become notes in their own right. The book note is the jumping off point for it. When I’m done with a book, the book note will have the links to the notes it brought forth, and the material that I didn’t in the end use for new notes. I keep the book note, and I keep the note with the highlights and annotations (it would resync from Kindle anyway), so I can always trace a note back to the book note and the location in the book itself.

Handwritten notes

I write some reading notes by hand on my BOOX Nova 2 e-ink device, as well as hand written marginalia, but I don’t have an easy flow bringing those to my notes in Obsidian yet. They are stored as PDFs on my e-ink device, and I need to bring them manually into Zotero, from which there then is a working flow to my notes.
This friction on the input side hinders regular use.

Over the years I’ve filled many note books by hand, not just with reading notes, but also annotations of talks, conversations and any other things I jotted down. Recent notes from the past day(s) I usually go through as needed and transcribe into my digital notes. I add them to my Day Log notes, which then can be a jumping off point to create additional individual notes.
Older notebooks, I have in the past scanned a lot of the key material, and have more recently scanned a few note books entirely. In my digital notes I have created an index file for each scanned notebook, where next to a link to each scanned page there’s a brief description of the content, and perhaps a link to relevant other material. That makes it possible to stumble across those notes in search.

Invitation to share

This post describes how I currently make notes from things that I read or wrote. It is a transcription and adaptation of a presentation I gave on April 3rd to the Readers Republic (video), an informal group of book readers around the world meeting every month for conversation. The question of note taking and learning came up as ‘So you’ve read a book, and then what?’ and a few of us volunteered to show what we do. I’m always interested in how other people organise their work, and I think that requires I also share how I work.

Essentially, this description of how I digest my reading is an invitation to you to write up your modes of working too.

Wired talks about the potential consequences of the EU Digital Markets Act which will enter into force later this year. It requires amongst others interoperability between messenger services by so-called tech ‘gatekeepers’ (Google, Apple, Facebook/Meta etc). The stance taken is that such interoperability is bad for end-to-end encryption. Wired uncritically accepts the industry’s response to a law that is addressing Big Tech’s monopolistic and competivity problems by regulating lock-in. Wired even goes hyperbolic by using ‘Doomed To Fail’ in the title of the piece. What stands out to me is WhatsApp (Facebook/Meta) gaslighting with the following:

“Changes of this complexity risk turning a competitive and innovative industry into SMS or email, which is not secure and full of spam,”

Will Cathcart, Meta’s head of WhatsApp, gaslighting the public about the DMA.

A competitive and innovative industry you say? Incapable of dealing with a mere rule change that just happens to break your monopolistic chokehold on your customers, you say? Nice dig towards e-mail and SMS too.

Meanwhile the non-profit Matrix has scoped out ways forward. Not easy, but also not impossible for the innovation and competivity inclined, as per the previous boasts of the competitive and innovative.

It reminds me of a session I with colleagues once had years ago with most providers of route navigation services, where it was about opening up real time traffic and road information by the Dutch government, specifically changes to roads. The big navigation providers, both of the consumer products, as well as the in-car providers, generally struggled with anything that would lead to more frequent changes in the underlying maps (adding stuff to dynamic layers on top of a map is easier, changing the map layer is harder). It would mess up their update cycles because of months long lead times for updates, and the tendency of the general public to only sporadically update their maps. This is the reason you still come across traffic signs saying ‘situation changed, switch off navigation’, because of your navigation provider’s ‘competitive and innovative’ attitude towards change.

There was one party in the room who already was able to process such deeper changes at whatever frequency. It wasn’t a ‘gatekeeper’ in that context of course but a challenger. It was the non-profit in the room, Open Street Map. Where changes are immediately rolled out to all users and services. Where interoperability is built in since the start.

“Situation changed, navigation on”, the type of response you’d expect instead of the usual ‘situation changed, navigation off’. This photo taken in 2016 or 2017 in Leeuwarden, where I’ve been working on open data. Image Ton Zijlstra, license CC BY NC SA

(The EU DMA is part of a much wider package of regulation, including the GDPR, expressing a geopolitical position w.r.t. everything digital and data.)
(I’m looking forward to the fits thrown when they close read the Data Act, where any consumer has the right of access to all data created through their use of a product of service, and can assign third parties to share it with. PSD2-for-everything, in short)

Favorited The Small and Starting Community Tool Gap on In Full Flow

Good questions I don’t know the current answer to either.

What tools are there if you want to provide a small, still forming group, an appropriate space for online interaction? Tools that are either very easy to self host, or cheap enough at the start to allow quick experimentation. Tools that don’t require a lot of skill to self host, tools that don’t throw up a (cost) threshold that surpasses the energy and will of a just budding group. There’s this precious moment in the evolution of a group, where there’s intention to constitute itself, but uncertainty about whether it will happen, whether those involved will indeed commit. Where commitment is slowly forming tit-for-tat. Where the group is still more network than group, but already in need of secluded space for their interaction, and not yet set firmly enough so that applying fixed costs would immediately make it collapse again.

What tools are there that allow you to interact online in multiple small groups? We all tend to be part of multiple groups, and e.g. if a fixed monthly cost would apply to all of them, that accumulates quickly. I already see that in my own ‘subscriptions’, which take constant pruning and balancing to justify their total cost to myself and our household. I very much dislike SaaS as a result.

…in the past few months I’ve had several moments that I wanted to bring people together outside certain social silo’s… It feels like there is a tool gap, or a price gap, for bringing small communities (or temporary project groups!) together.

As the web is so big, there are probably solutions out there that I don’t know of. Please share them with me

In Full Flow

Part of the conversations in the Republic of Readers group, are about what we do with what we read. I was invited to share a bit about how I (try to) process what I’m reading into something I can re-use over time in last weekend’s meeting. I couldn’t make it, but will do so in the next meet-up early April. As a first step I made a sketch of what my current flow and set-up looks like.

That’s not to say this is frictionless, and I’m not making claims as to its effectiveness. It’s what it is, warts and all. Also, any way you approach it, processing what I read, finding the bits that provide informational surprise, tying it to things I’ve written earlier, connecting it to the things currently relevant to me and hence to outputs, is intensive work. It is the work, and while I can strive to reduce friction on the interfaces between steps in my workflow, that work will always remain. Only through the work does reading gain meaning at all, because it is how you think things through.

Reading processing flow sketch. Click to enlarge. Image by Ton Zijlstra, license CC BY NC SA

Most of the removable friction in the reading-to-used-notes process is towards the left in the image. I use multiple devices, and getting notes in and out of them requires some jumping through hoops. It all ends up in Obsidian as my current note making tool of choice.

Only there the actual work starts: adding associations to highlights, lifting out bits and pieces from source texts and rephrasing them, creating the jumping off points for newly resulting notions. This is never a smooth process, and I usually struggle to allocate time for myself to think and write.

Output is a recombination of those notions into something that can be shared again, and if I have my notes in order it is a step that is less daunting than writing something from scratch. In the past months I have created several tools to make publishing something from my notes as frictionless as possible again.

Op zaterdag 12 maart vanaf 20:00 vindt weer een online Nederlandstalige Obsidian meet-up plaats. In een goed gesprek elkaars werkwijzen vergelijken, tips & tricks delen, en over het waarom en nut van persoonlijk kennismanagement met een tool als Obsidian. Iedereen is welkom. De link wordt op 12 maart hier, en in de Obsidian discord #nederlands aangekondigd.

Iedereen die Obsidian gebruikt of geïnteresseerd is in persoonlijk kennismanagement is van harte welkom.

Topic: Vierde Obsidian Meet-up
Time: Mar 12, 2022 08:00 PM Amsterdam

Join Zoom Meeting

Meeting ID: 839 7312 2854
Passcode: 967475