-
Thinking about page formatting and how to divide pages in Scrapbox is similar to designing the architecture of software or a database.
- For example, the concepts of MVC and database normalization.
-
Similarities:
- In Scrapbox, if you gather all the text in one file, it becomes difficult to reference from external sources. However, if you divide it too much, it becomes complex.
- This is similar to deciding how much to separate software code.
- Dividing it into smaller parts is also similar to database normalization.
- Both code and Scrapbox share the idea of “information being divided, having dependencies between them, and wanting to manage them in a human-readable way.”
- Codebase and knowledge base.
- In Scrapbox, if you gather all the text in one file, it becomes difficult to reference from external sources. However, if you divide it too much, it becomes complex.
-
Differences:
- Scrapbox is mostly directly operated by people, whereas databases can have different operations.
- For example, in NoSQL databases like Firebase Realtime DB, there is an approach of not normalizing the data.
- This approach may not make sense in Scrapbox.
- Scrapbox is mostly directly operated by people, whereas databases can have different operations.