In my 16 years of professional career so far, I’ve met, worked with, collaborated with, mentored and managed a considerable number of developers, both web and desktop. Most of the times, the developer was missing consideration that would otherwise help, secure, clarify and optimize workflow and efficiency.
Git is a system, which code development taps into, in order to document, automate, back up, collaborate on and organize teams of more than one developers. I will not mention the inner workings of Git and how to use it but I will approach this from a business perspective and how important it might be.
What’s important for the business
So let’s say that you hired one developer to help you with inner-company automation, code, a website and so on. The developer will write custom code to implement stuff for you. After 12 months, you get to a point where you want to onboard another developer. Let’s say that one of your projects has been completed 6 months ago and you would like the new developer to jump in and make changes. One way to do this is to have your main developer explain and train. While this is done though, time is being taken away from your dev from building actual things. What if the app and its code were documented somewhere where one would see info about it, a wiki maybe and the timeline of changes and code edits? That would be on Git.
Another example would be a case where two devs work on the same project at the same time. How would these two blend their code together into a solid and coherent system? What if one does something in the code that breaks the other one’s code? How would they know? If they use Git, one can blame, comment on, see changes and merge, fork and more, git will offer a full picture of things are progressing to the whole team.
On another note, let’s say that you want you developers’ code to be available to you, because you know, its yours to start with. You can keep backups yes, but what if you needed to see or show to someone, the timeline of development for that code? Git will allow you to see this as a backup and a history of the whole development work, which is great, its complete, its as it should be.
Not to mention of course that its quite helpful to the developers too, imaging one would stumble upon a problem that they know they fixed back in the day around that time. Having had git in place, they will be able to go into the commit history, go to that date, see the changes and find the solution.
Another way git can help the business is rolling out features to your various groups of employees or digital assets. For instance, let’s say that you have an office in the US and an office in Japan, you are sure the new feature is ready for the US but there are things still to find out about Japan. You want to roll out the feature or bug-fix ASAP in the US and wait a bit for Japan but you don’t want to fall behind on either of the two.
Git shines here, with dev ops and automations that are, these days, out of this world really, you can have a development git branch where your devs build code and commit to, a test branch where you QA the results and then one branch for US-production where you push features live and one for JP-production. So for the feature/bug-fix mentioned above, your devs would push first to US-production and wait a bit to push to JP-production.
Once the feature is pushed in the us-production branch and while Japan wait for their turn, new code might be built and new featured developed. Once pushed to Japan, they will get the latest stuff, so you don’t fall behind!
There are of course a log more benefits to using Git like SCRUM boards, built in issues and collaboration, automation with Kubernetes and a vast list of more reasons why your developers have to use Git!
How to get on board with Git as business
You can start with online services for Git like GitLab or GitHub, BitBucket and others with a free of paid account. Or you can set up your own server and install git systems there, like the hosted version of GitLab.