Ask anyone managing a database and they will tell you there is a lot you need to track outside of the database. You need to manage server configuration settings, user access info, and documentation, just to name a few things. And then there are all the testing code snippets and other software tools and setting you to need to keep in order. It can get messy and complex quickly.

The good news is that with a slight modification to your existing workflow, anyone managing a DB can track all the work that lives outside the DB using Git. At its core, Git is a DB for tracking changes in files, no matter what is in them. Not only can it help you keep track of your work locally, but it can also help you share your work and make onboarding new folks a lot simpler.

In this session we will explore:
- Implementing a basic Git workflow
- To CLI or Not CLI?
- Branching for separation of concerns
- Time traveling through previous work
- Sharing your work safely