This is quite a personal thing... I'm terrible at note taking and I've tried a few methods. I find organising this kind of "data" very difficult and I also find habit forming around note taking very difficult also. Finally, I always hated the idea of daily notes/journaling, so I resisted it for the longest time.
But when I finally started making a journal it was a lifeline. It works so well for me. I stop worrying about what I'm writing, how well I'm writing it, how I'm structuring it, where I'm storing it... and I just write it.
If it's something pertinent to what I"m working on, then it'll be a note from the last few days. Old notes, I just don't worry about.
I do have a page for "todo" type thing and I'm still working on that and I also write "proper" documentation separately. But daily notes are a huge win for me.
thomascountz · 1h ago
It's difficult for me to read past the sentiment of the author's language, which is unfortunate, because there are interesting ideas here.
At any rate, my takeaway isn't anything to do with whatever the author considers a "daily" note or not, but about how the way we structure and synthesize our thoughts, alters the things we make.
For example, if in the creative process, I create an audience for myself (i.e. by thinking of sharing my notes), that may or may not introduce productive constraints to my process. On one hand, it could force me to better articulate my thoughts. On the other, my inner critic could preclude important insights.
stephenlf · 1h ago
I like that “one note per issue/resolution” thing. I have an .md in our company’s main internal app’s repo which is just a bunch of tips and patterns for doing DevOps tasks. At the bottom is a section called “## Useful Shell Script,” a collection of scripts each in their own block quote. The approach work well for our small team, but it couldn’t scale. Having a personal repository with this sort of pattern would be very helpful. Thank you!
sp33der89 · 1h ago
I disagree with the author, but I also get the impression that their view of notes is fundamentally different than mine so there's that.
I like the way LogSeq implemented daily notes, UX wise. It's an infinite scrolling page where you can add and edit dailies, so I end up "doomscrolling" my daily notes and re-reading them a lot more often than in other apps.
TooSmugToFail · 1h ago
Daily notes are my life line.
If you’re managing any fairly complex organisation and handling multiple threads on variable time horizons, daily notes can be an immensely useful tool.
spankibalt · 44m ago
I indulge in daily notes but make and organize them (mostly) topically. Dates are obfuscated, "discreete" if you will; they are, or can always be made, visible if so desired.
The notion of "not asking the same question twice" is laughable to anyone who interrogates different structures based on the same parameter(s), e. g. for comparative purposes. And daily notetaking based on a date-based organization principle is of course widely applicable, e. g. for (project) diaries, "to-be-sorted" infodumps, etc.
But then again, I find most programmer's notions of notetaking to be quite tedious, often bordering on the literally void. ;)
But when I finally started making a journal it was a lifeline. It works so well for me. I stop worrying about what I'm writing, how well I'm writing it, how I'm structuring it, where I'm storing it... and I just write it.
If it's something pertinent to what I"m working on, then it'll be a note from the last few days. Old notes, I just don't worry about.
I do have a page for "todo" type thing and I'm still working on that and I also write "proper" documentation separately. But daily notes are a huge win for me.
At any rate, my takeaway isn't anything to do with whatever the author considers a "daily" note or not, but about how the way we structure and synthesize our thoughts, alters the things we make.
For example, if in the creative process, I create an audience for myself (i.e. by thinking of sharing my notes), that may or may not introduce productive constraints to my process. On one hand, it could force me to better articulate my thoughts. On the other, my inner critic could preclude important insights.
I like the way LogSeq implemented daily notes, UX wise. It's an infinite scrolling page where you can add and edit dailies, so I end up "doomscrolling" my daily notes and re-reading them a lot more often than in other apps.
If you’re managing any fairly complex organisation and handling multiple threads on variable time horizons, daily notes can be an immensely useful tool.
The notion of "not asking the same question twice" is laughable to anyone who interrogates different structures based on the same parameter(s), e. g. for comparative purposes. And daily notetaking based on a date-based organization principle is of course widely applicable, e. g. for (project) diaries, "to-be-sorted" infodumps, etc.
But then again, I find most programmer's notions of notetaking to be quite tedious, often bordering on the literally void. ;)