This btw is the maker time/manager time problem pg wrote about. Making needs 4 hour chunks because anything less tends to increase entropy rather than decrease it in any non-trivial knowledge work project. So anything that lowers that lower limit is a big win.
Conversation
My suspicion is, a good KPI for a knowledge tool is minimum threshold of time required to make a negentropic update to it, with every halving of the threshold increasing its capacity to hold positive-interest-rate knowledge repos by an order of magnitude.
1
1
37
So a tool with a 2h minimum can sustain a 10x bigger positive-rate knowledge base with the same budget of people/money than a 4h minimum. I suspect for Roam, a very suitable project may get it down to minutes, and for a typical project, maybe 30min.
Something like that.
3
24
Hmm trying a 2x2 :diagram in roam. It is pretty janky but close enough to usable that for simple ones, I'm likely to use native rather than import from a more complex tool.
2
2
28
One sign I'm achieving some sort of "hedgehog closure" is that I'll find a thought in my pre-Roam notes I'm not sure I've captured yet, and when I go to add it in a page I'm not sure exists yet, I'll find that the page and the capture both exist. Falling necessity of deduping.
1
21
Okay, I started using Roam on Nov 26, so I'm now almost 3 weeks in. I seem to be entering a more difficult middle phase where it's all about resolving mergeconflicts. Lots of page merges and clean-ups today.
1
10
I am experiencing a kind of grind that I'll call a "Windows 95 to Windows XT" experience. My current state is a complex thing (Windows) built on a primitive simple thing (DOS) and I have to now go back and rebuild foundations in light of the clarity achieved at the complex levels
2
10
This is definitely not as fun as the first 2 stages. I think I'm going through a double freytag process here.
1. Discovery (pre-Roam) increasing entropy collection
2. Sensemaking (stage 1 Roam)
3. Valley (mergeconflicts and rationalization)
2
16
Hmm. Conflicted about what to do about the content I started putting into a few months back. While Roam is clearly a much more powerful paradigm, I do like RS's cleaner presentation and collaboration/permissions model.
Quote Tweet
I guess I leapfrogged past Notion, and there were a couple of other tools I started using like paper.supply but in view of this, I don’t think others hit the right mix. Hey @vidy___ you still working on your thing?
Show this thread
2
2
(in the quoted earlier tweet in this thread, I mistakenly referred to it as paper dot supply)
I was briefly kicking the tires on that a few months back, but unfortunately, it didn't take as a habit the way Roam appears to be doing for me.
Quote Tweet
Hmm reading.supply is nice. Clean collaborative document archive creation space. HT @tobyshorin for the find. Kicking the tires now. So far I like it. Cc: @vidythatte another product in introvert-toolkit space, kinda complementary to what you’re working on.
2
3
It'd be nice if reading.supply or something like it were bolted onto Roam as a sort of classic publishing/sharing front-end.
Replying to
I was briefly being pretty evangelical about reading supply, but the enthusiasm dropped rather quickly once I realized the creation workflow friction is too high... on par with say google docs. But still, there's some stuff there that's interestingly different from Roam.
1
4
Unlike Workflowy, which I think has been strictly superseded by Roam. Again a nice product, but simply beaten comprehensively by a better one. For now. I don't think it's down for the count yet.
Quote Tweet
shit, moving my workflowy list over to roam was a single cut and paste operation... this is not good news for them, they're probably toast if they don't differentiate fast
2
6
Important threshold: it’s now easier to create a page linked off the right existing page for a one-liner thought than to tweet it and then postprocess the tweet. Took some practice, but I do it routinely now. Roam has hacked the tweeting impulse. Like Uber hacked taxi-hailing.
3
3
22
When I compare to effort in late 90s (hand code new html page, edit existing to link, and ftp to home page site) the effort level to create a meaningfully linked page has fallen fallen faster than Moore’s law. I now do it on phone for 1-liners. Amazing.
2
15
Kinda like what git did to code commits and forks. Made it really cheap and got us to continuous deployment/continuous integration.
Roam is CD/CI for brain.
5
1
32
