Interdependent Thoughts

10 reactions on “”

1. Your text-expansion muscle memory is not going to serve you well when you take on your first client from Tanzania.

   • 😀

2. I too prefer to decide when I want to pay more to upgrade software but I have kept TextExpander 5 running along because I find it easier than Alfred for most snippets. For one thing, I don’t have to summon Alfred first. Maybe I should be transferring my snippets more actively, to be ready for the fateful day.

   • Yes, I also kept TextExpander 5 running, but of course that’s only postponing the inevitable. If you set Alfred to automatically expand snippets by keyword, and start Alfred at start-up like you would have to do with TextExpander, then you don’t need to summon Alfred first. It just works exactly the same way as TextExpander (I’m also transferring the snippets unchanged).

3. My friend Ton Zijlstra recently wrote about switching from TextExpander to Alfred, prompted by TextExpander’s move to a subscription model. I found myself in the same boat a while back, but wasn’t entirely happy with the way Alfred handled that kind of text expansion. I replied to Ton, pointing out that I preferred TextExpander because “I don’t have to summon Alfred first”.
   Dumb, as I learned by actually reading about Alfred Snippets in a bit more detail and as Ton gently pointed out.
   Time to start transferring those snippets over, which is also a good opportunity to clean them up a bit, sort them out a bit, and consider a collection wide affix.
   Thanks Ton for prompting me to do this.

4. I’ve now migrated all my text snippets from TextExpander to Alfred. With Alfred set to automatically expand snippets upon typing a keyword anywhere, it behaves the exact same way as TextExpander. TextExpander has been useful to me over the years, but their new subscription model is not for me.

5. Back up hassle

6. Ik las over Ton’s overstap van TextExpander naar Alfred. Ik heb al jaren geleden afscheid genomen van TextExpander, inderdaad vanwege het abonnementsmodel. Ik heb geen problemen met terugkerende abonnementen, maar dan moet de reden wel passend zijn. Voor een programma wat op slimme wijze je sneller laat typen, zag ik niet de meerwaarde van een abonnement. Ik stapte over op Typinator. Als ik me goed herinner, was de belangrijkste reden omdat Alfred in die tijd al wel snippets had, maar die waren nog niet zo doorontwikkeld.
   Jeremy Cherfas noemt het ook in zijn post, sommige tekst-uitbreidingen zijn intelligenter dan alleen tekst. Er zitten berekeningen in of ze maken gebruik van scripts.
   Tenminste, dat wás bij mij het geval. Over de jaren merk ik dat ik bepaalde tekst-uitbreidingen niet meer gebruik. Mijn meest gebruikte uitbreidingen zijn vrij eenvoudig van aard. De grootste complexiteit zit soms in een datum, of een keuze uit een paar opties.
   Ik gebruik zowel Alfred als Typinator. Misschien wordt het eens tijd om de mogelijkheden van Alfred nader te onderzoeken. Als ik weer een programma minder kan gebruiken, dan laat ik dat niet na. Ik gebruik al jaren het Powerpack van Alfred, het wordt tijd om eens te zien wat het nog meer kan.
   <!–

   –>

7. I’ve been using Obsidian a little over 100 days now. So, with over three months of daily use it’s good to review the experience. I will do this in some detail, and it will span several blogposts. To explain both the evolution over time, as well as how I currently work with Obsidian in practice in a more detailed way, as Frank (rightly!) requested.
   My system leads the use of tools
   First off, a key point to make. I am using a system for myself to plan and do my work, maintain lots of things in parallel, and keep notes. That system consists of several interlocking methods, and those methods are supported by various tools. What I describe in my review of 100 days of using Obsidian, is not about Obsidian’s functionality per se, but more about how the functionality and affordances of Obsidian fit with my system and the methods in that system. With a better fit with my system and methods, I can reduce friction in my methods, and reduce the number of tools I need to use in support of those methods. At the same time, the use of a new tool like Obsidian influences the practical application of methods, it creates a different daily practice. Those shifts are of interest as well.
   What I started with
   The image below shows you how my overall system of work and taking in information looks. It’s a personal knowledge management system, that both takes care of the networked nature of making sense of new information and evolving interests, as well as the more hierarchical nature of working on projects and executing tasks. Both start with my general notion of where I want to be headed (‘goals’).

   I used different tools for different parts of that image:

   Excel (orange) for: listing goals (3-10 yrs out), the 3 month planning cycle I keep (along the lines of ’12 week year’), the habits I want to maintain or introduce, and tracking of those habits and project progress/fulfillment.
   Things (red) for: areas of my life I’m active in, projects within those areas, and tasks in those projects.
   WordPress (darkblue) for: daily logs (which I started keeping end of April this year, on an internal WP instance), week logs (internal draft blogposting), and of course for public blogging itself.
   Evernote (blue) for: a list of all my current interests/favourite topics, all types of note taking, related to my work/projects and my information diet.
   Other tools (grey) come into play for feedreading (Readkit), blocking time (Nextcloud calendar in Thunderbird), book reading (Kindle, Nova2), keeping references (Zotero since June, Evernote before that)
   While evaluating my system, I tried Obsidian
   In the spring I had started evaluating my system. I found I was not keeping up several parts of it, had fallen out of practice with a number of elements, and had changed some of my practices without adapting the flow in my tools. It had therefore suffered in its usefulness. Being at home because of the pandemic allowed me to allocate some time to take a better look, and to start testing some changes. On the tool side of that evaluation, I want to get rid of Evernote (as a silo and single point of failure) since some years.
   One change in my system I was experimenting with, was keeping better atomic notes about the core concepts and key elements in how I work. Late last year I thought a bit about atomic notes, i.e. cards with individual snippets, and bringing those collections of snippets and the process of curating them and threading them into e.g. a blogpost or a line of argumentation. In January I came across Zettelkasten and took a closer look, in the spring I read a book about Zettelkasten and knew I wanted to adopt parts of it into my system (linking notes first and foremost, and storing references in a better way). That’s when I started using Zotero to keep references, and stopped doing that in Evernote (Zotero can take website snapshots and store them locally, something I used Evernote for a lot. On top of it if you give Zotero a reference it will find and store a PDF of a scientific article, very useful to read more deeply).
   I started to keep atomic notes, sometimes called ‘evergreen notes’ which I to myself now call Notions, capturing concepts from my work (so not work related notes, but conceptual notes) first in both WordPress and Evernote simultaneously. WordPress (a local instance on my laptop, not online) because I already used it for day logs since April, and it allows relatively easy linking, and Evernote because it is much easier to keep notes there than WP, but linking in Evernote is much harder. I also played with some note taking tools, and that’s when I came across Obsidian. It immediately felt comfortable to use it.
   How after 100 days Obsidian has covered my system
   After over 100 days of Obsidian my use of it has expanded to include a much larger part of my system. Along the way it made my use within that system of Things, Evernote and almost Excel obsolete. It also means I sharpened my system and practice of using it again. This is how the tool use within my system, with the use of Obsidian in green, now looks

   Obsidian now contains some 1200 mark down files. 500 are Notions, atomic notes almost exclusively about my own concepts and other core concepts in my work, in my own words. Mostly taken from my own blogposts, reports, and presentations over the years. The other 700 are some 115 day log / week log / month maps, about 100 proto-notions and notes that contain conceptual info to keep from other sources, and some 500 work and project related notes from conversations and work in progress. This sounds as a very quantitative take, and it is. I have in the past months definitely focused on the volume of ‘production’, to ensure I could quickly experience whether the tool helped me as intended. I think that monitoring the pace of production, which I’ve done in the past months, will no longer be relevant by the end of this year. I used the quantity as a lead indicator basically, but have been on the lookout for the lag indicators: is building a collection of linked notes leading to new connections, to more easily creating output like blogposts and presentations, having concepts concisely worded at hand in conversations to re-use? And it did. One very important thing, central to the Zettelkasten method, I haven’t really tried yet however, which is to use the current collection as a thinking tool. Because I was more focused on creating notions first.
   On Obsidian as a tool
   There are four things in Obsidian that are to me key affordances:

   it is a viewer/editor, a fancy viewer/editor, on top of plain markdown text files on my laptop. It builds its own local database to keep track of links between notes. Whatever happens to Obsidian, my data is always available.It being ‘just’ a viewer is important because Obsidian is not open source and won’t be. There is a potential open source alternative, Foam, but that tool is not yet developed enough.
   being ‘just’ an editor means using regular text files, it feels like coming full circle, as I have for the most part been note taking in simple text files since the late ’80s. Textfiles always had my preference, as they’re fast and easy to create, but it needed a way to connect them, add tags etc., and that was always the sticking point. It means text files are available outside of Obsidian. This allows me to access and manipulate notes from outside Obsidian without issue, and I do (e.g. on mobile, but also with other software on my laptop such as Tinderbox that I used for the images in this post).
   it makes linking between notes (or future links) as simple as writing their filenames, which is supported by forward search while you’re typing.
   it shows graphs of your note network, which to me is useful especially for 2 steps around a note you’re working on.
   I use Obsidian as simple as possible; I do not use plugins that are supposed to help you create notes (e.g. the existing Zettelkasten and Day log plugin), because they make assumptions about how to create notes (how to name them, which links to create in them). I created my own workflow for creating notes to avoid functionality lock-in in Obsidian: day logs are created manually by keyboard shortcuts using Alfred (previously TextExpander), as are the timestamps I use to create unique file names for notes.
   Timeline of three months of Obsidian use
   Below is a timeline of steps taken in the past months, which gives you an impression of how my use of Obsidian in support of my system has evolved.
   November 2019 I discuss the concept of cards (i.e. atomic notes), curation and writing output
   January 2020 I first looked at the Zettelkasten method and some tools suggested for it. I mention the value of linking notes (possible in Evernote, but high friction to do)
   May 2020, read the book about Zettelkasten by Sönke Ahrens, adopted Zotero as a consequence.
   7 July started with deliberately making Zettelkasten style atomic notes in WordPres en Evernote in parallel, to move away from collecting as dumping stuff in your back yard. Atomic notes only concerning my concepts in my work.
   8 July started using Obsidian, after having just started creating ‘evergreen’ notes
   15 July having made 35 atomic notes, I make a new association between two of them for the first time.
   28 July I’m at 140 conceptual notes. I named the collection Garden of the Forking Paths. I switched my digital tickler files (a part of the GTD method) from Evernote to Obsidian. I had stopped using them, but now it felt normal again to use them. The post I wrote about this, was made from atomic notes I already had made beforehand.
   5 August I find I haven’t used WordPress anymore for my day logs ever since starting with Obsidian, and that I also added week logs (an automatic collation of day logs), and monthmaps (a mindmap at the start of the month listing key upcoming things and potential barriers). My Evernote use dropped to 4 notes in 4 weeks, whereas it was 47 the 4 weeks before it. After almost a month of Obsidian, I am getting more convinced that I am on a path of ditching Evernote.
   12 August I renamed my ‘evergreen’ notes, that contain my concepts mostly, to Notions, as the generic word notes doesn’t make a distinction in the character of some the things I’m putting into notes.
   12 August I write a first long form blogpost made from Notions
   13 August Added Nextcloud synchronisation of the note files, allowing mobile viewing and editing of notes
   31 August I keep track of tasks in Obsidian and drop Things. There was a time I always did such things in straightforward text files. Being able to do so again but now with a much better way of viewing and navigating such text files and the connections between them, makes it easy to ‘revert’ to my old ways so to speak.
   13 September I am at 300 Notions. These first 300 notions are mostly my notions, the things that are core to my thinking about my own work, and the things I internalised over the past 25 years or so, of doing that work. I expect that going forward other people’s ideas and notions will become more important in my collection.
   13 September I describe how I make notions and notes
   September / October I increasingly use my conceptual Notions as reference while in (online) conversations.
   5 October I gave a client presentation (about the Dutch system of base registers) pulled together completely from existing Notions.
   7 October added a ‘decision log’ to my note keeping.
   16 October 100 days in Obsidian, 500 Notions and about 700 other types of notes.
   16 October reinstated a thorough Weekly Review (a component of GTD) into my system.
   21 October I gave a brief presentation Ethics as a Practice, the second this month pulled together from existing notes.
   This all as a first post looking back on 100 days of Obsidian.
   Part 2: Hierarchy and Logs
   Part 3: Task management
   Part 4: Writing connected Notions, Ideas, and Notes
   Part 5: Flow using workspaces
   Part 6: Obsidian development vs my usage

8. I am finally getting to learn AlfredApp Workflows. Previously they looked rather daunting to me.
   Since I moved to a new laptop I’m learning to do more with AlfredApp (it is Mac only, and I use the paid PowerPack option). On my old laptop I first only used it for custom search, such as finding a business on Open Street Map. Later I added the automated expansion of text snippets, which saves me a lot of typing during the day.
   AlfredApp also allows you to make Workflows, where you string together triggers, inputs, operators, actions and outputs to automate tasks on your machine. I had previously looked at Workflows but they seemed complicated to me, judging by some example workflows I downloaded that weren’t at all clear to me. Early this morning I came across this video of Automating All The Things, where Aron Korenblit talks with Chris Messina about using Workflows (it was early and I did not jot down where I found the vid, in someone’s RSS, mastodon stream or someplace else, so HT to whoever pushed it in my stream)
   this is just a screenshot from the video that links to the video on YT, not a video player: I didn’t want to embed YT video.
   This morning I reckoned I wasn’t going to watch a 87 minute video, but I was wrong (though I did jump forward a few times). Chris takes Aron through the basics of building your own Workflows, and I now get what they are and how to build my own. First I’ve added some fairly easy things, like having typing ‘read’ open up my fresh articles in my TinyTinyRSS feedreader instance, or typing ‘blog’ followed by a type of post, e.g. ‘blog bookmark’ open up the correct editing window for it. Next, I will be thinking through my local routines and context switches, and how I might be able to assist myself by automating them. The video starts with a few quick tips on how to make AlfredApp easier to access and use for yourself, so it can get embedded in your muscle memory.

Comments are closed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)

URL/Permalink of your article

Mentions

• 💬 Ton Zijlstra
• 💬 Ton Zijlstra
• 💬 Frank Meeuwsen
• 💬 Back up hassle
• 💬 Ton Zijlstra