📖 Principle of atomicity
# Write notes to include only one idea
Establishing a networked note-taking system requires reconceptualizing what makes up a note. Primarily, we are concerned here with notes which contain ideas: Notes on other types of information such as biographical data or shopping lists are not necessarily the most useful within the network (although biographical data can be usefully linked to particular ideas as a form of citation, as this digital paper strives to demonstrate). Critically, however, these ideas can and should come from a variety of sources. Taking note of the ideas we encounter in our day-to-day life, not just academic literature, is an important way to diversify the knowledges we produce.
Working with ideas is where the strength of the network happens. Unlike traditional idea-notes where one note is meant to capture the entire context of a reading, lecture, or observation session, however, networked note-taking relies on other notes for context. This means that individual notes are much shorter than traditional notes and are meant to capture one clear idea, or what Tietze (2013) describes as the principle of atomicity, where the note-taker must keep relevant notes close together, but ultimately “separate concerns from one another”—a concept which he derives from software engineering (para. 24). Matuschak (n.d.-b) adds that atomicity is useful because it makes connections across notes much more specific.
This principle can be difficult to enact because it requires drawing boundaries around what makes up a complete idea, a concept which has blurry boundaries to begin with. Overly-atomized notes do not stand on their own and require too much traversing across the system to understand, while notes which are not atomized enough are difficult to link to others. In general, however, it is helpful to keep in mind that the principle of iteration encourages reviewing and revising notes as they are added to the system.