I'm constantly experimenting with it! The downside of it being so flexible is that it can take a while to figure out the best system.
At the moment, everything goes into one database called 'Notes'. I enabled the 'Created at' and 'Edited at' properties. I also have multi-select properties for themes (e.g. rationality, productivity, economics, etc) and for type (e.g. random thought, blog idea, resource, article, tool, etc). I also have a checkbox property called 'processed' - and I filter the view of the table to only see the unticked items. Everything I add is by default 'unprocessed' (i.e. unticked) - this allows me to add stuff from the web (with the web clipper) and quick random thoughts without worrying about immediately sorting them. Every so often, I go through everything that is 'unprocessed' and sort it (add tags, finish reading it, add highlights or more notes, links to other notes, etc) and once I'm done I'll tick the 'processed' box so it's hidden from the default view.
I 'favorite' the notes I use most regularly (e.g. I have one called 'useful info' which has stuff like my health insurance number, wifi passwords, etc). Otherwise, I navigate by searching, or by filtering on certain tags.
I'm planning to gradually build this out into a relational system (e.g. creating a 'project' table and linking the notes to relevant projects, etc). I try to 'organize opportunistically' (as described in Part II C here - retrieved this from my Notes table in Notion!) as I find most of my attempts to impose a top-down structure are not flexible enough.
What I use:
There seems to be some evidence that a norm of helmet-wearing discourages people from cycling. When people don't wear helmets, they are taking on some personal risk, but by challenging the norm it could mean that more people take up cycling. This is likely to make cycling safer (fewer cars on the roads, drivers are more used to cyclists, safety in numbers at intersections etc), and so the need to wear a helmet is reduced.
I'd prefer to live in a world where more people cycle and helmets aren't (as) needed (like in European cities such as Berlin and Amsterdam), so I tend to feel grateful towards people who don't wear helmets.
This is great, I can see it being really helpful for me to consciously think about which of these I'm optimizing for (or am willing to sacrifice) when writing. I got confused by the introduction of the term 'density' in the section on trade-offs, as this isn't represented in the RAIN framework. Is density just a sub-consideration of accessibility or are you considering it in its own right?
FWIW, there seems to be a trend in my corner of the AI safety community (CHAI) to move away from the term 'values' and towards the term 'preferences', I think for similar reasons.