this post was submitted on 16 Mar 2025
1246 points (99.1% liked)
Technology
66687 readers
4595 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Right. But you can’t do that in a live system like google docs. You can have a workflow to export copies, but the live doc is the one bigquery and linked docs utilize to function against your app. It’s actually a feature of the same tooling that makes using them like a database possible that causes it to not be versionable. So even if you export copies as you update it, you can’t move the system back to those copies without breaking other parts of the system.
Other systems for modeling data have better version control for running parallel versions of models if you need to recover how data had been constructed in an older state. It’s an incredibly bad idea to do this with Google docs at scale