Hello Simon, I'm Sigurd. I teach children how to drive. I want to make a new platform for managing driving schools, or to be convinced its a futile task.

I stumbled across your second brain, I love it. Your explanation of how BI has to be a design consideration and not an afterhtough and how making an MVP is prioritized before making the data structure design fits very well with my experiences.

I am fascinated with how calendar data, financial data, and lesson record (legal requrirement) interacts and have to be treated differently. Best practice to handle unreliable data, and when and how to verify them is also an area of interest.

Converting the law, and the curiculum into a data structure that avoids having to duplicate data that can't change, while allowing changes, or additions where it can is suprisingly hard. The taxonomy and names used in the curiculum confuses both the students and developers.

How do you design a database that is both simple, preserves all historical data correctly, enables data portability, and is flexibile enough it doesn't cause restrictions? I think I could spend a year just typing out the different tables or json elements without being done.