I’m intrigued by Zettelkasten, that Roel Groeneveld describes in his blog. Zettelkasten means filing cards cabinet, so in and of itself isn’t anything novel. It’s all in the described process of course, which originates with systems thinker Niklas Luhmann. I recognise the utility of having lots of small notes, and the ability to link them like beads on a necklace, which is much like the ‘threading cards‘ I mentioned here recently. A personal knowledge management process is extremely important, and needs to be supported by the right tools. Specifically for more easily getting from loose notions, to emergent patterns, to new constructs. Balancing stock and flow. Zettelkasten coming from a paper age seems rather focused on stock though, and pays less attention to flow. Crucially it encourages links between notes, a flow-like aspect, but to me often the links carry more meaning and knowledge than the notes/nodes it connects. The reason for linking, the association that makes a link apparent is an extremely valuable piece of info. Not sure how that would find its place in the Zettelkasten process, as while links exist, they’re not treated as a thing of meaning in their own right. Also some of the principles of the process described, especially atomicity, seem prone to creating lots of overhead by having to rework notes taken during a day. That type of reworking is I think best done in the style of gardening: when you are searching for something, or passing through some notes anyway, you can add, change, link, split off etc.

Tossed out filing card cabinets of the Manchester City Library (NH/USA), image license CC BY SA

In terms of tools, I am on the look out for something other than Evernote that I currently use. What I like about it is that it ‘eats anything’ and a note can be an image, text, web page, book, pdf, or a drawing, which I can add tags to, and can access through scripts from e.g. my todo tool, etc. Zettelkasten is fully text based in contrast. As a strong point that means it can be completely created from plain text files, if you have a tool that allows you to create, edit, search and put them in an overview extremely fast. But very often ideas are contained in images as well, so dealing with media is key I think. The Zettelkasten tool The Archive is worth a try, but lacks precisely this type of media support. Devonthink on the other hand is way over the top, and let’s one loose oneself in its complexity. The Archive keeps things simple, which is much better, but maybe too simple.

Favorited Wissenschaftliche Distanz und Aktivismus—Notizen zu Will Steffen und Hans Blumenberg by Heinz Wittenbrink

Herzlichen Dank, Heinz, das du uns im Blog mitnimmst in deiner Suche, und Gedanken über den eigenen und praktischen Umgang mit dem Thema Klimanotstand.

Zur wissenschaftlichen Haltung gehört eine distanzierte Perspektive auf die Zeit—sowohl auf die erdgeschichtliche Zeit, mit der es die Erdsystemforschung zu tun hat, wie auf den zukünftigen Fortschritt der Forschung selbst, in der Erkenntnisse immer wieder revidiert und weiterentwickelt werden. Diese Perspektive unterscheidet sich von der lebensweltlichen Perspektive auf die Zeit und auf historische Ereignisse, die praktisch beeinflusst werden können. Wenn die Wissenschaft aber durch ihre eigene Entwicklung mit diesen lebensweltlichen Ereignissen, und zwar mit extrem bedrohlichen Entwicklungen konfrontiert ist, dann lässt sich die wissenschaftliche Distanz nur noch zynisch aufrechterhalten. Die homogene, neutralisierte und unendliche Zeit der von der Wissenschaft untersuchten Ereignisse und des wissenschaftlichen Fortschritts lässt sich nicht mehr von der endlichen Zeit der historischen Erfahrung und der politischen Praxis trennen. Angesichts apokalyptischer Ereignisse, deren hohe Wahrscheinlichkeit sich mit der überhaupt möglichen wissenschaftlichen Sicherheit voraussagen lässt, werden die Möglichkeiten, diese Ereignisse zu verhindern, zur wissenschaftlichen Priorität.

Heinz Wittenbrink

Bookmarked Guide to Internal Communication, the Basecamp Way

Found via Peter Rukavina. This guide contains a lot of interesting nuggets that apply to my company too. There are some longstanding differences in preference in our team about real time communications and remote working. Me with a strong preference for remote and asynchronous as default. This guide may serve well for further internal conversations.

At Thingscon last month in Rotterdam, I sampled various talks and sessions. I ended up somewhere halfway in a contribution by Sarah Kiden (currently a research fellow at University of Dundee). She mentioned the ‘radio in a bucket’ project in Uganda, as illustration how to bring technology into the hands of more people by removing some of the thresholds and fears. Radio in a bucket is precisely that: it’s everything you need to create a local radio station, packaged in a bucket. The bucket serves as a way to appear familiar to those who normally don’t interact with (high) tech devices. The familiarity of the bucket as everyday object removes some of the apprehension of using the technological devices in the bucket.

Hide Tech as it were, not High Tech.
I liked this example for the balance it was trying to find. Regularly when technological complexity is hidden from someone using the technology, it takes away agency. I cannot even change the lights on my car these days, because the entire front is integrated into a single object. Nor can I access all the sensors and software in my car. It renders me helpless whenever something needs fixing on the car.
The Ugandan examples is about hiding some of the technological complexity to stimulate agency. To take away initial apprehension, do I dare touch the device, so curiosity can take root (what happens if I flip this switch?).

What tech should be packaged in a ‘bucket’ for your to adopt it more easily. For instance distributed alternatives to social media platforms. What Hide Tech would encourage you to do more?

Felienne Hermans, a Leiden University teacher started a series of postings about the mistakes she feels she made on the tenure track. I look forward to her reflections. In her kick-off posting she lists the mistakes she plans to look into, which I quoted below in full. Reading the list, there is much there I think that applies to life in general (e.g. 11, 12), being a professional (e.g. 3,4), being an entrepreneur (e.g. 6,8), and being an employer (e.g. 1,7, 10), not just the tenure track. Or at least by the looks of it, it matches my experiences in those roles.


So here, without any order or further ado is a list of mistakes I made on the tenure track, which I aim to all expand into blog posts over the next few weeks….

  1. I made no agreements with my direct supervisor on basically anything
  2. I had no real (concrete) research plan
  3. I had no system to track time
  4. I had no system to manage todo items
  5. I did not want to co-teach courses
  6. I took enormous risks spending time on irrelevant things (which *by sheer luck* turned out to be beneficial)
  7. I treated all students like they were mini-Felienne’s
  8. I had no system for managing ideas
  9. I had no system for managing research I read
  10. I did not spend effort on creating a group
  11. I did not understand personal factors in working with others (students and colleagues)
  12. I was not present enough in the university

(I met Felienne at the CoderDojoNL conference last November, where we both gave key-notes. Since then I read her blog.)