Matsui-lab (@utokyo_bunny) keeps code, models and shared datasets in sync across laptops, lab servers and cloud: Git for code, S3 for storage, DVC tracking dataset versions with MD5 hashes in Git. Full step-by-step setup 💡
In Japanese!
hubs.la/Q04z1FdJ0
- @nishat_NSS six habits for reproducible single-cell projects: Git + DVC, http://params.yaml, http://dvc.yaml, http://dvc.lock, and the mistakes that silently break real genomics work. Built to survive manuscript revision ✨ hubs.la/Q04z1xVV0
- Phat Vo from @fintech24h_com treats data lineage as AI security infrastructure: DVC keeps an audit trail of what went into every training run, alongside layered defenses and continuous monitoring. Provenance first 💪🏼
- Evgeny Levashov's guide to ML storage on S3: naming schemes for datasets, features and model weights, DVC for dataset versioning, MLflow for artifacts, Feast for features, and lifecycle rules to control costs ✨ hubs.la/Q04z1pXk0
- @datalaria's four pillars for taking a model from Jupyter to production: Git for code, DVC for data, MLflow for models, CI/CD and drift monitoring. Ties it all to EU AI Act compliance too 🚀


