So the hierarchy looks like this: 
1. Commit points to a Tree 
2. Tree points to Blobs (files) and other Trees (folders) 
3. Blobs hold the actual data.

I spent years using Git on "autopilot" before I realized I had no clue how it actually worked. I knew the commands the add, the push, the commit. but, the "why" was a total black box.

The biggest surprise? Git isn't actually a "code" tool. It’s a content tracker.

I asked the Google Gemini app for a simple diagram of how Git reuses data to save space, and it gave me...

cows?

🐄

Every data pipeline is a bet.
Not a bet about tools, a bet about how the system will fail.

Most engineers build for the happy path:
API up. Schema stable. Volume reasonable.
That’s not where production systems live.

Your pipeline is not broken; your assumptions are.
rajanand.substack.com/p/your-pipe...

No, 2026 is the current year, not next year.
Happy new year!