Plenty of debate out there on where to put curly brackets in code. I'm not here for that, though I have opinions on it. Be consistent and have some degree of hierarchy, and the rest will sort itself out.
Let's talk about paper notes. Specifically, using brackets for organization, even if you already have another form. Only talking about the quick bullet-ish style of note, not flowing prose or code.
I know this sounds odd, using a workaround made for the limitations of old machine language parsers on fluid natural language, but I have reasoning. It's not about parsing (which humans are famously good at), it's the restrictions of physical writing.
Let's consider the alternatives.
First, leading indicators are impossible to make consistent. Writing on paper is stream of consciousness, so you might not realize something should be a section or a subsection until you've already written it down, especially if you're taking live notes. Categorization of almost anything is best done after you already know what it is, not before.
This includes indentation and bullet point styles, but also changing text size, color, or letter style since those also are decisions you have to make before you start writing. Editing them in is nigh impossible cleanly, possibly requiring adjusting the entire line or scrunching in the start. Bad for readability and writing speed, both of which are already struggles for handwritten notes.
Leaving empty lines works extremely well, but it's fragile. Space is always at a premium on paper when editing is so slow and you can't predict how much you'll need. You should leave empty lines to be filled with new thoughts, not cram yourself into smaller space to preserve some semblance of organization.
What about retroactive modifications like highlighting and underlining?
They're more practical, but require a fundamentally different movement than writing. Going from dense append-only letter formation to drawing straight lines around existing text is a context switch, and context switching while notetaking is going to crash your train of thought. You can drill it in with muscle memory if you prefer, but I'd rather take the easy route.
Enter brackets. Brackets are slim and typically appended to the end of the line, so you can add them anywhere. It's like in code, they complement indentation, but can be slipped in retroactively without rewriting if necessary. There's other potential trailing indicators such as colons, but brackets have the flexibility of being optionally explicitly closed and are more readable if you already program in a language using brackets.
Finally, they're quick and lightweight. Zero interruption of flow, simply tack one on as you realize a thought needs a subsection, or rub out the single character if it becomes unnecessary. No changing writing utensils or hand movements.
For me, who has spent years staring at code marked with brackets, the readability increase and low effort compared to the typical ways of marking sections is unmatched.
I don't know how helpful it'll be if you don't program, but give it a try. If you don't like it, it's a one character erasure at the end of the line.
- Rew
Nightly Notes
The topic of when to use paper or digital notes in general is hotly contested, and I'm still finding the line myself. Still, locking down simple notations in either system works wonders. I should write about markdown one of these days, tainted as it's become by these unprecedented times.
I can't stand bullet journaling because it's entirely based on only partially adjustable leading indicators, but they were onto something with the simple notation. If you found this post interesting in the slightest at all, the original video is well worth watching for the sheer elegance of the system.
- Rew