3 ms·
>A lot of other solutions I've seen are more like concept maps, which are great for project management, but not great for knowledge bases. I've never understoo
by jpfed 11y ago
>A lot of other solutions I've seen are more like concept maps, which are great for project management, but not great for knowledge bases.
I've never understood this preference; would you be willing to explain it? It seems almost exactly backward to me: I model tasks as trees of sub-tasks, and knowledge as a general graph of connected concepts.
- Alex3917 11y agoSo all knowledge can be seen as connected, but all knowledge can also be put into hierarchies. Concepts and how those concepts are related is something that people come up with, rather than being an inherent property of the universe. The idea of forcing yourself to put knowledge into hierarchies is that it makes your thinking more clear, makes it easier to remember where things are, and perhaps paradoxically makes it easier to see how things are related. (Or at least highlights certain types of relationships that are only visible in the context of hierarchies.) I'll admit it's pretty weird at first to only get one root node, I think it took me a couple years to get used to that. But once I embraced it the benefits quickly became clear.