Hacker News new | ask | show | jobs
by conaws 2341 days ago
Problem w evernote is that file is bad unit of organization.

In a meeting with 4 people, discussing three big ideas, related to two projects, what file do you put the note in?

In Roam that's not even a question you have to ask, all info in each paragraph goes to all the right places

3 comments

This is definitely a problem I run into. I’m having a team meeting about Project X, and someone mentions that a particular task is waiting for something from Project Y.

The only way I’ve found to handle this is manual. Note the dependency in the meeting notes, then process the notes after the meeting creating relevant todos elsewhere. But that’s only maintainable if you don’t have a lot of work on at the same time, or a lot of dependencies - and we find ourselves back at lean.

Too much work is too much work, and no amount of automation is going to fix that. Furthermore, life is messy, and there is no universal way of structuring that mess. The more mess there is, the harder it will be to live with it. So reduce the mess to the point you can live with it, rather than trying to structure it.

I don't use files, I use tags. I have 2 notebooks to differentiate notes that I want synced to my mobile devices, but really that's not needed.

You can tag any note with multiple tags and then use saved filters to always find notes which are in a given tag. All of this used to work a lot better (evernote search has been getting consistently worse) but it still works fine.

You can use multiple tags, but the granularity is still page level. To continue on Conor's example, you'd have, say, a note for your whole meeting, with 3 sections for each agenda point. And you'd have 3 tags.

But then when you want to see information pertaining to a given tag, it means that the content on that meeting note is 66% irrelevant. That doesn't happen in Roam.

But in the current state of the app sharing a note shares your entire DB, its an awesome tool but I'm unable to find a way to create a secondary DB without creating a new account.
Capability is there, but UX sucks for both sharing single pages and creating seperate workspaces.

Been working on both this week.

could you point me to the doco