Why Your Data Team Needs Version Control
2024 ж. 15 Мам.
2 681 Рет қаралды
The fastest route to problems as a data team is going straight to Production.
It feels easy in the short-term, but becomes a mess in the long-term.
But it’s shocking how many teams still do this.
So in this video, I’ll explain why your data team needs to be using Version Control so you can:
- Stop losing changes
- Release code faster
- Work better as a team
Thank you for watching!
►► The Starter Guide for The Modern Data Stack (Free PDF)
Simplify the “modern” data stack + better understand common tools & components → bit.ly/starter-mds
Timestamps:
0:00 - Intro
0:28 - Track Historical Changes
1:32 - Automate Your Workflow
2:54 - Work Better as a Team
Title & Tags:
Why Your Data Team Needs Version Control
#kahandatasolutions #dataengineering #versioncontrol
►► The Starter Guide for The Modern Data Stack (Free PDF)→ bit.ly/starter-mds Simplify “modern” architectures + better understand common tools & components
HI Michael, Thanks for Sharing this very important and useful information , I am relatively new to working with git, can you please provide some resources/use cases, where the merge conflicts arise and how to resolve them. I have been watching some videos around this topic, and mostly either 'merge commits' or 'rebasing' is used to fix this. I wanted to understand which should be the preferred approach on a project where multiple developers are working concurrently,
Nice video!! I know that this comment will sound dumb, but in our team we have to add who add which code line, and we are using git to track the code history, I will say in the next daily that we should drop that little block of code mentioning who changed it 😅
Lol don't worry that's not dumb at all. I've been on teams where we've done that exact same thing and have worked with clients recently who also do it. It's pretty unnecessary though once you have your git workflow in place. Good luck!
HELP