2
Design guidelines
Fabien Benetou edited this page 2026-04-10 10:05:07 +00:00

This page explains design decisions.

Everything is a scaffolding

There is currently no complex large database in use. This will create problem if the project scale.

This is done knowingly. A problem to solve tomorrow will be a traceable experiment to learn from. If a problem is solved before it happens there is no trace left for others to learn from.

See #52

No optimization except for learning

If there is a choice between something more efficient but harder to understand, always chose the easier to understand option.

Onboard users as future contributors

Always provide a path, even if only as documentation, or comment, on how to modify more.