Interesting:
Docs is the result of a joint effort lead by the French 🇫🇷🥖(DINUM) and German 🇩🇪🥨 governments (ZenDiS). We are always looking for new public partners (we are currently onboarding the Netherlands 🇳🇱🧀). Feel free to reach out if you are interested in using or contributing to docs.
https://docs.numerique.gouv.fr/login/
#docs #opensource #eu #europe #france #germany #netherlands #collaboration #fosdem
Right up until you are doing compliance and governance and you realize docs are actually a terrible terrible source of truth for any automated systems. We’re 3 years into a project at a healthcare company to rip google sheets and docs out of our apps and replacing them with Postgres, bigquery, dbt and dagster.
It’s simply not okay to have your database be something anyone with write access to a doc can fuck up a formula by accident on. Your medical bills being maintained by random formulas on dozens of linked spreadsheets maintained by hand by random people on different teams is part of why they are impossible to unwind. By the time someone audits it, it’s printing different numbers than when your bill was rendered and it’s version control doesn’t work to roll it back without breaking dozens of other things.
I’m in the engineering business. We have a PDM system that we check-in copies of component 3D models, PDF drawings and DOCs. Once your team has collaborated enough, you have a copy…once a week/day/hour depending on your preference. That way you can collaborate and keep frozen records and rev controlled documents.
No, because with the above you can have rich objects in databases (for example, a dynamically updated list of medical events, each with all the attributes I want, attachments etc.), and almost arbitrarily deep nesting of databases.
The idea to have databases with pages is one of the key features that made notion successful. It allows to structure knowledge without duplication, in addition to provide some other no-code features.
I love the docs ability to create databases from my docs. That would be super useful for work and research activities.
Right up until you are doing compliance and governance and you realize docs are actually a terrible terrible source of truth for any automated systems. We’re 3 years into a project at a healthcare company to rip google sheets and docs out of our apps and replacing them with Postgres, bigquery, dbt and dagster.
It’s simply not okay to have your database be something anyone with write access to a doc can fuck up a formula by accident on. Your medical bills being maintained by random formulas on dozens of linked spreadsheets maintained by hand by random people on different teams is part of why they are impossible to unwind. By the time someone audits it, it’s printing different numbers than when your bill was rendered and it’s version control doesn’t work to roll it back without breaking dozens of other things.
I’m in the engineering business. We have a PDM system that we check-in copies of component 3D models, PDF drawings and DOCs. Once your team has collaborated enough, you have a copy…once a week/day/hour depending on your preference. That way you can collaborate and keep frozen records and rev controlled documents.
Oh, you mean a spreadsheet?
No, because with the above you can have rich objects in databases (for example, a dynamically updated list of medical events, each with all the attributes I want, attachments etc.), and almost arbitrarily deep nesting of databases. The idea to have databases with pages is one of the key features that made notion successful. It allows to structure knowledge without duplication, in addition to provide some other no-code features.
Spreadsheets are not even close.
Exactly. Engineering research test write ups and results could be quickly searched for in a good document database.