Hello everyone, it’s Ray. Today I’m going to share why Git is so a lot required.
Firstly, have you once encountered that situation that something comes up when you are coding, it could be that your mom calls you, or even more serious that you forget to pick up your girlfriend.
Unfortunately, at that very moment you happens to do debugging or develop a new feature.
When you finally get some free time to proceed your coding, holly shit… something goes wrong! It’s hard to debug among a sea of code especially when you don’t know where to start.
Or, sometimes when developing a new feature, unluckily it happens to affect the current feature and cause some error. When we realise that searching from nowhere might lack efficiency and want to go back to the moment when the new feature is not yet started, our good habit of saving file regularly just cover the light at the end of the tunnel.
At this moment, we regret that we didn’t’ use git earlier.
When you encounter some emergency during coding, or you want to start a new feature based on current one that works, you could simply use git to save it, and after that you could go there whenever you need. Also, this kind of saving takes the precedence over the built in saving function of editors, or IDEs that you use. In other words, even though you’ve saved the file on your editor or IDE, you could still go back to the point that you saved with Git.
In other circumstance, except for the small project that you could complete on your own, it required multi-collaboration when it comes to a big project. Have you thought of how to efficiently collaborate with each other? After all, coding is sort of delicate work. One typo sometimes could keep the function from working properly.
At this circumstance we always use Git to do the integration. Imaging that you do your portion on your own computer, and upload to a mutual folder after you finish it. Other team member do the same thing, and Git could do the integration.
So to a coder, Git seems to be an integral tool.