The only TWO ways you should be using Git

Bending the Clean Architecture principles

Introduction

When we’re building any kind of software, we usually plan and organize our thoughts in some sort of process. While planning ahead is good, I think it can go to waste, especially if you’re not keeping up with the latest and greatest tools/technologies. This plan relies on these technologies, so they are equally as important.

If we look back on how things used to be done, we used to focus mainly and exclusively on our source code. Employers used to go above and beyond to hide their precious source code and license their applications.

Our businesses and industry evolved drastically. Now, our precious SC is considered just another tool available in your arsenal. Anyone can code anything but what’s distinctive is quality, speed, and efficiency.

Git helps you manage your SC and is the entry point to most of our CI/CD pipelines. Here’s how you most likely should use Git and Why:

What

Git tracks your team’s project files as they change over time. It stores this multi-user information in a Repository. Grouped file changes in a repository are Commits, and Heads are like the pointer to a specific commit. You can create parallel universes…