Why should large datasets not live directly in Git?
PICTURE THIS: HASH MAP
Simple meaning
Git is designed for small text diffs, not multi-gigabyte Parquet dumps.
WHY — DVC instead of guessing?
Why interviewers care about DVC:
on DVC.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Git is designed for
small text diffs, not multi-gigabyte Parquet dumps.
- 2Repos become slow and
clones become painful.
- 3DVC or object storage
with hashes keeps Git usable while still versioning data.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Git is designed for small text diffs, not multi-gigabyte Parquet dumps. Repos become slow and clones become painful.