▲ | atoav 3 days ago | |||||||
Yes, but the average Obsidian user may or may not know what a database is an why they should care. As an engineer I like precise language, but we should not forget that multiple audiences require multiple levels of explainations. Otherwise it is a bit like saying "all monads are functors" when trying to make your reader care for investing time and energy into understanding the concept of monads. The problem there of course is that explaination is circular: without the reader knowing what a monad or a functor is they can't understand the explaination. A good explaination gives you the technically correct slogan in the beginning (for the advanced readers) and then explains the words and what you can do with such a database and why you should care. Many explainations skip the last step and leave that part as an exercise to the reader. | ||||||||
▲ | slightwinder 3 days ago | parent [-] | |||||||
> Yes, but the average Obsidian user may or may not know what a database You can't constantly optimize your communication for the least educated recipient. Obsidian is full of technical, specialized terms. If you don't know a word, research it. And database as a concept is common knowledge today. Everyone will have the word heard in news at least, most will have a rough understanding of its purpose. And people using obsidian are usually not the most uneducated, there have a certain level of technical expertise. Most will also know and understand the dataview-plugin. | ||||||||
|