‹ go back

Morse Code Context.

Published 06 December 2020 at Yours, Kewbish. 1,988 words. Subscribe via RSS.


This post is unlisted and has been archived. This doesn't represent my best work; please check out the posts listed here instead.

Introduction

Hello, and welcome to another episode of Kewbish talks about notes and knowledge for no reason whatsoever. I’ve somehow fallen into the corner of the interwebs vaguely describable as ‘knowledge twt’1. Reading papers, especially CS-ish design (read: not entirely incomprehensible) ones, is kind of nice. Perhaps this habit stems from the lab reports we constantly have to write, but I find reading through them therapeutic, in a way.

These papers have a host of ideas spanning many disciplines and areas of thought. That’s something I kind of like, as someone very inexperienced in the field. HCI, as I think it’s properly called, spans a large breadth of thought. Luckily, most of it is the sort of thing that balances yet complements the science-focused learning I do for school. I find it fun to read papers (yes, I’m a massive nerd), especially these, where I don’t have to constantly do math or think about theory (though that can also be fun).

One of the ideas I’ve seen over the last couple weeks was the concept of context, and either persisting or deleting it. How does one encapsulate the context of a moment, be it branching browser history or leaving a trail of thoughts between processing sessions? The concept is striking: when looking through things I’ve written even just a year ago, there’s often a question of why I even thought it was a good idea. Re-entering, or even getting a glimpse into, the frame of mind I was in then would be very interesting for reflection2.

I’d like to bookmark my thoughts and keep a giant log of posts that have sparked a rabbit hole of thought, but I also think it’s kind of charming to rediscover posts on their own. It’s a slow, perhaps luck-based, process, and I’m not guaranteed to recover a key article, but it’s more organic. Increasing serendipity or something.

I’m vaguely free from school at the moment, so I might write a bit about some thought-chains I’ve had surrounding HCI topics. Maybe these posts’ll get published, maybe they won’t. Please don’t take these seriously; I wanted to record random things I was thinking about and I thought I may as well publish them.

Dots and Dashes

The first inspiration for this chain of thought was a tweet involving Cal Newport’s Morse Code Method. It’s from a while ago, but it has some interesting points regarding contexts, and context switching.

In the article, Newport touches on a efficient style of notetaking: the Morse Code Method. The only two symbols are, aptly, a dot and a dash. While skimming through and processing content a first time, mark each main point with a dot. Supporting ideas are denoted instead with a dash. It’s important to maintain momentum while processing the literature, which makes the entire process a lot quicker than the typical ‘read and annotate at the same time’ technique. Not breaking the reading flow also would definitely reduce the amount of context switching required.

Newport then suggests annotating and pulling together additional notes after the process of reading, making it a distinct second step. I see this as playing into active recall somewhat, albeit in a very short-term, very non-spaced repetition way. Dots are reviewed for their striking-ness, and discarded if now irrelevant. This process of reviewing and redoing notes after having a different view on the paper definitely helps with filtering. I find that notes before or while learning a topic are a lot less polished and full of (usually unanswered) questions instead of actual new thought. After taking the time to understand and condense information3, the third step to this strategy-of-sorts, notes are usually more direct and dense.

A Search for Serendipity

Sometime when I was supposed to be doing work, I had a thought. I haven’t tried it myself, nor have I had the idea long enough to evaluate it, but I think it might be interesting. What would happen if the second and third steps of the above method were eliminated? There might be something intriguing there if the need to paraphrase and keep annotations was gone, and we just had dots and dashes scrawled in page margins.

Obviously, if a line inspires a groundbreaking idea, that might warrant more permanent storage. While there’s some use to writing everything I take out of a given text or chunk of information, I feel like it makes things a lot more rigid. Rigid, as in, I now have one interpretation (hopefully mostly thoughts that are original and add to the material) in front of me. If I never looked at the text itself again, I might never try to reinterpret and rethink the ideas with my current worldview. After all, I’ve read it once, and I now have these very comprehensive notes, so why should I? Perhaps a book isn’t quite good enough to warrant a second reading, and maybe the notes are good enough™.

But I feel like there’s a lost possible serendipity. Sure, finding ideas anew without rereading is certainly possible, especially if you’ve densely interwoven your notes with other thoughts, as in a Zettelkasten. There’s the chance that you might stumble upon an orphaned or unlinked markdown file. However, I don’t know if there’s enough of a reason to revisit and reevaluate thoughts this way.

If I was just presented with a trail of dots and dashes, and perhaps had to filter out information again, I’d probably develop a whole new set of ideas. Coming from the possible added perspective of a couple months or years, this might be a bit better than static (evergreen?) notes. There’s a sense of wonder and clicking through rabbit holes the first time one finds a particularly well-linked and well-connected thread of thoughts. I’m not sure if I can document that all the first time, and I’m also not sure if I’d be able to remember key points that were most interesting again.

I was thinking of building another personal Chrome extension lately. Instead of keeping more fleshed-out annotations in a bank, simple dots and dashes were placed in the margin of a webpage. (CSS-wise this might be a bit tricky, but let’s not discuss the technical details.) I’d not keep proper thoughts; just little circles and lines. Perhaps these could be reordered with shortcuts, and maybe even combined in different contexts. It might also provide insight through time by track placement of these pico-annotations.

This, however, does come with the same caveats as footnote 33. While it does increase the possibility to rediscover and readd new ideas, ideas will be filtered out and left in the dust at times. These might not be as ‘big’ as some of the other points, and not get passed on to the next generation of notes. Context, as well, might well be lost. If a thought from generation 1 of a note only happened due to connections with other similar thoughts in context of mindspace 1, what happens if mindspace 1 is entirely dissimilar from mindspace 2 when taking generation 2 notes?

Mapping Context

The idea I’m trying to explore is the persistence of context. On one hand, a constant, rigid context (if well-written) provides stability at the expense of some additional commitment and friction when trying to add to them. Not only does one have to recomprehend the text or work at hand, but one also has to try to reenter the mental location they were in when first processing information. The ideas surrounding previous ideas may unknowingly invade newer thoughts, tainting them retroactively, in a way.

I don’t want to lose my place, or my frame of mind. An ideal situation would be infinite memory, and an equally infinite and expandable notation for my current context. (But that might be a tad overwhelming.) Leaving a breadcrumb trail of similar thoughts that led to a specific thought would increase the amount of notetaking friction at one point in time, but may help in the future. There’s no point to do context-heavy notes for a topic that you know won’t be referenced in the future, so that might reduce the amount of labour if you’re fully aware this for a one-off thing. But how does someone evaluate this ‘one-off’ness? You could argue that no notes should be made at all, if it’s only to be used in the extremely short term.

On the other hand, completely throwing away trying to recall the context, and focusing on just the current interpretation gives some more flexibility for the future. With a way to remember which points and which areas made you think last time, it might be an interesting balance to investivate. The main points and supporting points you picked out last time would still be available to see, but perhaps the interpretation could be different this time around, or maybe it’s largely the same.

I’m wondering how I can reflect a context of a moment into my notes without creating too much extra friction force against taking notes. Currently, the persistent pico-annotation idea, combined with perhaps note versioning but with fresh starts every so often, is my best thought on the topic. Perhaps another day of diving into Twitter threads might be in order.

Conclusion

Context, especially wih regards to processing, is an intriguing area of thought. A lack of context forms a certain atmosphere, if I can call it that, and a large amount of it creates an metalayer. The amusing screenshots that fill up my Imgur are generally taken out of context. Notetaking often happens without context - especially if it’s just raw information without reflection. Automatically added metadata (file creation time, EXIF data) adds another layer of searching possibilities, and a feeling of meta-organization. I have no idea whether context is absolutely essential or not, but I can see how it (over?)shadows interpretation. Just earlier, I was annotating an act of a play for class again (I did it in a different format that I wasn’t satisfied with the first time round), and found myself essentially reframing past thoughts slightly. Maybe it’s just me, and the way I work.

Tech Twitter is a very deep rabbit hole, and is very good at leading me into long clickchains. However, I can justify reading papers and being extremely nerdy about this because it’s semi-productive, right? It’s led me to investigate a lot of literature I wouldn’t have without it, and is strangely therapeutic, so that’s that.

I suppose this is a nice round place to end off. This was indeed full of tangents and small points, but I think it’s a nice way to frame my thoughts for later (look, context!). I have nowhere else to put them, and this essay’s vaguely technical, so here it shall stay.


  1. That being said, I also don’t have a Twitter, which makes things slightly less addicting / more difficult to check in on all the content, but here we are. It’s also interesting to note how seemingly everyone in HCItwt seems to know, or at least somewhere reference the others. It’s a Roam graph of people - which I suppose is the essence of a social network. ↩︎

  2. And the same process will happen in two or three years when I return to these posts. It’s a cycle, and it’s a process - but that doesn’t mean I won’t cringe. Well, at least the cringe now is several magnitudes less than two years ago: will this pattern continue? ↩︎

  3. It might be interesting to see how this process would play out if intermediary layers were scrapped. Perhaps if they were on scratch paper, intended on being thrown away or (a less harsh approach) filed into a ‘cold’ archive for very unfrequent retrieval, it might reduce the pressure of making ‘good notes’. However, there’d come the very real possibility of not recording any new thoughts that might have helped with future iterations of a concept, or losing existing ones in the condensing process. ↩︎ ↩︎


‹ go back