I honestly think that the windows phone development experience is where Microsoft majorly shit the bed. The sheer volume of breaking changes (and the severity of those breaks) meant rewriting a non-trivial amount of your app from version to version. I know multiple developers that just dropped support for windows phone as a result.
It’s almost like people that use the tools to the best of their ability will produce higher quality outputs. This is a new tool like we’ve never seen before with a low skill floor to use it. We don’t know what the skill ceiling is yet.
Maybe you’re the person I’ve been looking for but I’ve yet to find someone that actually maintains a zettelkasten that isn’t a researcher/author and doesn’t come to the conclusion that it’s a huge waste of time and energy.
I just had the same thought. I searched for the book mentioned, and as soon as zettelkasten popped up I lost interest. I've read about zettelkasten so many times, but I can't get myself to actually try it, it seems like doing organization for the sake of declaring "I'm very organized", regardless whether it's efficient or not.
I had this same issue with my original zettelkasten system in org-roam. Also it had become just, a locally indexed wikipedia.
This book is probably not the greatest resource for establishing a zettelkasten, but it is very good at demonstrating how a good externalized writing system is critical for getting good learning done and finding unique insights. Also, it addresses the wikipedia issue I had specifically. As another person mentioned in this thread, making the notes more like proper publishable writing (even if just a sentence) made a big difference.
I've found it somewhat valuable in two ways and unhelpful/misleading in another:
1. Making small notes is so intuitive and low-pressure. I was already essentially doing before but in the form of various lists of "ideas" or "thoughts on _blank_". You can't reliably decide where you would've put something, it becomes a mess. The fact its a single directory of .md's with a phrasal titles is a great organizing constraint.
2. Being able to find old thoughts/ideas easily and link them together lead to the clarification of a lot of my more unique ideas because of the ad hoc link-language that emerged.
The big problems are the rabbit hole of manic articles promising too much, and the fact that after a while you simply have too many half-baked two-year-old notes that the whole thing becomes limiting and your declare note bankruptcy.
So, first, most would say the purpose of a zettelkasten is to write. The book goes into this, that your notes eventually just get incorporated into manuscripts, and that your notes should be written as well as if you were writing a manuscript itself.
However, what really clicked with me about the book was the hypothesis that true human thinking can only be done externally, through writing, due to the limitations of our brain as a platform. The book lists out things like recency bias and short term memory limitations that get in the way of proper, structural thinking that results in actual insights. Whereas maintaining a zettelkasten, or a simulacrum of one at least, externalizes your thought process and allows you to achieve genuinely your maximum potential for thought.
The arguments went beyond the normal ones about the recorded benefits of note-taking for learning, memory, and creativity, and got into the aspects unique to a zettelkasten that make it an enabler for thinking. However the book also pitches this as a productivity boost for authors and researchers, and doesn't really seem to care about people who are just learning for the sake of learning (but it does make a solid case that building a zettelkasten makes learning more fun).
Personally I've been reading criticisms of the book as a way to learn how to maintain a zettelkasten that I agree with: it's not specific or clear enough, and it defines too many different kinds of notes (and not all at once; some note types are defined like 3/4 of the way through the book). For me it was just a very convincing argument to stop trying to make my brain do things it isn't good at - stop beating myself up trying to memorize super detailed facts, let my external system handle that. Stop worrying about forgetting bits and bobs of the various books I've read, let my external system slowly create a map of ideas of everything I'm reading. Stop over-optimizing all my note taking systems and just scratch shit into a paper pad, to be indexed as a good zettel later (or just thrown away if I decide it's not helpful).
So, though I do intend to use this system to fuel my blog, I think I'd still find value in it just in feeding the conversations I have as well. I'm deeply interested in non traditional politics, leadership, and activism, and with this system I've adopted I'm finding myself make connections I don't think I'd have made before; for example this very idea of externalization and scaffolding of human thought as a means to make up for our flaws, I'm finding similar threads in all sorts of things I read now.
If you're interested in zettelkasten, I would recommend a different resource for learning how to actually set one up (just, the internet plus chatgpt is probably fine, plus some FOSS software). I will say, if it's taking too long, whatever you're doing is too complicated. It should take a single click or button press to make a new note, and it should be very easy to scan through your notes and make links every once and a while, and making a link should be no more than a highlight, a button click or press, a search, and a confirmation. If you're anything like me, you may spend more time setting something like this up and agonizing over it than you will using it... that's why I moved from org-roam to trilium, so I could just stop hyper optimizing and start using the damn thing.
My reading of it also violates the Boy Scout Rule. That is to say: if improving some portion of the codebase would make it better, but inconsistent, you should avoid the improvement; which is something that I would disagree with.
I think adherence to “consistency is more important than ‘good design’” naturally leads to boiling the ocean refactoring and/or rewrites, which are far riskier endeavors with lower success rates than iterative refactoring of a working system over time.
The problem with small refactors over time is that your information about what constitutes a good/complete model of your system increases over time as you understand customers and encounter edge cases. Small refactors over time can cause architectural churn and bad abstractions. Additionally, if you ever want to do a programmatic rewrite of code, with a bunch of small refactors that becomes more difficult, with a single surface you can sometimes just use a macro to change everything all at once.
This is an example of a premature optimization. The reason it can still be good is that large refactors are an art that most people haven't suffered enough to master. There are patterns to make it tractable, but it's riskier and engineers often aren't personally invested in their codebases enough to bother over just fixing the few things that personally drive them nuts.
If improving some portion of the codebase would make it better, but inconsistent, you should avoid the improvement. Take note, file a ticket, make a quick branch, and get back to what you were working on; later implement that improvement across the whole codebase as its own change, keeping things consistent.
if you have some purported improvement to a codebase that would make it inconsistent, then it's a matter of taste, not fact, whether it is actually an improvement.
I'm not fully convinced that those devices don't create noise at full power. But one issue still remains: LLMs eating up compute on the device you're working on. This will always be noticeable.
Are trying to say it’s not possible to write terms that give them the ability to sync your history without also letting them mine and sell all the insights from it?
From a technical level, exactly how is Apple mining your browsing history and bookmarks if they are end to end encrypted and they don’t have access to it?
There’s probably some compliance requirement that it’s technically possible to set it up without an internet connection, so they leave it there, but make it unreasonably difficult for a majority to do it.
reply