Logseq is amazing software but it’s coming to an Interesting turning point at the moment. It’s great for unstructured writing ✍️, interstitial journaling and expanding your working memory. It is helping you connect what you encounter today with what you knew before but forgot about.
An analogy come to mind, from software. Before the distributed git version control model, people needed to checkout files they wanted to work on before they could edit them. No one else can check them out at the same time, to prevent merge conflicts. But that created a bottle neck in how people could interact on a team. Git changed all that, letting people check out code freely, unblocking collaboration . Merging became more painful yes but we saw merging could be asynchronous .
Similarly I think logseq opens up your mind checkout restrictions as well. You dont need to impose early structure on your thinking that can otherwise block you from getting started.
And interestingly , unlike git where you must eventually merge your distributed branches, in Logseq, you are building a thought network that doesnt really need checking in and merging seems to happen in tge background . However it does appear to require your intervention. Here's where we have two interesting issues at play.
For one, logseq is currently slowing down I suppose for people with large graphs, and opening Logseq these days takes quite some time, in particular, I think, if you have a remote graph that must first be checked for integrity. A low level merge I suppose, to prevent sync related data loss issues of the past .
But until the slow start issue is resolved, myself and I imagine others with large remote graphs too, have turned to writing outside of logseq, merging back in later.
Im currently writing this in Hey. Usually I have been using another Notes app too. And I have these scattered notes which I realize I have not added to logseq recently because of the extra overhead recently.
Im looking forward to the so called database update that is on the horizon, to help with start up speed, but I see an even bigger soft problem as well. And thats pruning.
When we sleep, we myelinate some connections and chop others. This is learning and pruning. Sometimes with Logseq, i feel like my second brain hasn't slept for months 😂.
I think I have realized, that "this", writing and such, and conversations (that lead to writing blog posts), are the way to help mature and crystalize open loops in your Logseq that would otherwise perpetuate, disconnected from reality.
An analogy come to mind, from software. Before the distributed git version control model, people needed to checkout files they wanted to work on before they could edit them. No one else can check them out at the same time, to prevent merge conflicts. But that created a bottle neck in how people could interact on a team. Git changed all that, letting people check out code freely, unblocking collaboration . Merging became more painful yes but we saw merging could be asynchronous .
Similarly I think logseq opens up your mind checkout restrictions as well. You dont need to impose early structure on your thinking that can otherwise block you from getting started.
And interestingly , unlike git where you must eventually merge your distributed branches, in Logseq, you are building a thought network that doesnt really need checking in and merging seems to happen in tge background . However it does appear to require your intervention. Here's where we have two interesting issues at play.
For one, logseq is currently slowing down I suppose for people with large graphs, and opening Logseq these days takes quite some time, in particular, I think, if you have a remote graph that must first be checked for integrity. A low level merge I suppose, to prevent sync related data loss issues of the past .
But until the slow start issue is resolved, myself and I imagine others with large remote graphs too, have turned to writing outside of logseq, merging back in later.
Im currently writing this in Hey. Usually I have been using another Notes app too. And I have these scattered notes which I realize I have not added to logseq recently because of the extra overhead recently.
Im looking forward to the so called database update that is on the horizon, to help with start up speed, but I see an even bigger soft problem as well. And thats pruning.
When we sleep, we myelinate some connections and chop others. This is learning and pruning. Sometimes with Logseq, i feel like my second brain hasn't slept for months 😂.
I think I have realized, that "this", writing and such, and conversations (that lead to writing blog posts), are the way to help mature and crystalize open loops in your Logseq that would otherwise perpetuate, disconnected from reality.