Emerging overview with structure notes
I want to share the gist of a few recent happy moments of Zettelkasten note-taking with you and find out what you do in your work to achieve a similar effect -- or if all of this is totally new to you.
Against all odds, I did manage to write a Zettel note or two during 2017. I did not process all (any) of the interesting books I read, but I took notes while working on my current app project, The Archive. In the meantime, I read @sfast's draft for the 2nd edition of the Zettelkasten Method book and gave more thought to structure notes.
Back when I started with the archive, I created
INDEX notes to, well, create topic index notes. They mostly contained definitions and a few outgoing links (my archive was very small back then, so there was not much to link to at first). Along the way, I ditched the concept of "index" notes and only recently rediscovered the utility of structuring topics with dedicated structural notes.
What I found out was:
- The old
INDEXnotes have to be "refactored": I have to extract the definitions into dedicated definition notes and leave a link to them in the index. This could revive the index notes.
- Taking notes for ongoing research and grouping the resulting notes in overviews immediately gave an additional feeling of closure. Even more so than adding a link from a large project buffer.
- There is no such thing as merely collecting source code; in my case, most of the interesting notes of 2017 consist of interpretations of Apple's programmer documentation, code snippets and samples, and collections of tips from around the web regarding text editing -- in short, stuff that's suitable to be assembled into blog posts for my programming blog. More than 80% of the programming notes contain far more than source code snippets. I can append interpretations and reasoning even to something as unambiguous as code.
Here is an example of a growing structure note about typewriter-mode text editing that is also a project outline:
Title: Approaches to a Typewriter text component ID: 201707081109 Tags: #nstextview ##outline #typewriter-mode ## Conceptual - [] Essence of the Typewriter Mode - [] Flavors of Typewriter Mode - [] Overscrolling is essential for typewriter modes - [] Regular scrolling without overscrolling described - [] Animate programmatic scrolling in NSScrollView ## Implement scrolling - [] Implementing Two-Sided Overscrolling in a NSTextView. You'll need that for typewriter scrolling with focus lock. - [] Implementing One-Sided (Bottom) Overscrolling. That's useful for non-immersive situations like text editors or note-taking apps that provide an extra nice user experience. - [] NSScrollView scroll notifications. You need to adjust the insets as the view resizes. - [] Avoid NSTextView scroll to bottom of document in typewriter mode ## Implementation TextKit components - [] Subclassing NSTextStorage - [] User-initiated text change callback from NSTextStorage - [] Keeping the insertion point centered - [] Typewriter scrolling without flashing scroller knobs Details: - [] Line height in a NSTextView - [] Debug output for NSTextView width and insets. Used in _The Archive_ to find out why changing window sized and fullscreen mode didn't work properly.
Although this is tagged
##outline, it's not yet outlining a comprehensive guide. It's work in progress, but I know it's going to be a writing project already. Not every structure notes has this tag; them being structure notes is not marked in any way.
Here is a shorter one on an implementation detail that requires a few code components to change at the same time:
Title: Working with NSTextFinder find bars in NSTextViews ID: 201712021110 Tags: #nstextview #nstextfinder - [] How to validate NSTextFinder actions - [] How to write a custom `NSTextFinderClient`: use a thin adapter for `NSTextView` - [] Use `NSTextFinder` from anywhere by bypassing `performTextFinderAction`, using a custom selector instead. - [] Reset `NSTextFinder` on programmatic string changes (obsolete with a custom `NSTextFinderClient` setup) ## Programmatically remote-controlling find bars - [] Close the find bar programmatically for `NSTextView`s - [] Invoke the find bar from different view components
The last example is grouping together 1 high-level explanatory note and various annotated implementation details. I know I'll need this in other projects, and I know I'll have forgotten about the intricacies by then. So this is a good entry point into the topic of "How to use NSTextFinder". You can see from the Ids how this little cluster grew. over the course of one day.
I know @sfast is using structure notes a lot for quite a while; I think he's tagging all of them to denote "this is structural", which I apparently don't. (Making it harder to assemble a list of structure notes, like I wanted to have today when I drafted this conversation.) I only recently discovered their utility and am still experimenting, and I think I'll add meta-tags to them, too, to cover the case when I know that I did write a structure note sometime last week, but cannot remember what the topic was.
- Anything that comes to mind which I overlooked so far?
- Do you branch off of detail notes and assemble overview notes of some sort?
- How do you make sure you use your Zettel notes?
Author at Zettelkasten.de • http://christiantietze.de/
It looks like you're new here. If you want to get involved, click one of these buttons!