Git

"Version Control Your Code"

Kommentare: Git has been my introduction to version controlling my coding work. Now that I use Git, I'm never going back. Git is too important.

Vorteile: Git is my go-to for version controlling my code for web development. When I first switched from no version control methods to Git, it felt like a magic trick with how you can manipulate the timeline of your work. For example, you can make egregious mistakes and rest assured that, even if you delete your whole project, almost any action can be restored or undone. The concept is with any change you make to your project, you commit the change to a Git repository as a sort of point in a timeline. With this commit, Git automatically keep tracks of a timeline of changes made to the project, so you're able to use Git as sort of a time machine to go back (or forward) in time. You can even create different "branches". This is like an alternate timeline. Want to try something crazy? Just create a different timeline (branch)... if you don't like what you tried, then you can always go back to your original branch. It's like nothing happened. But, if you like the change, just merge that change back into your original branch. Now your offshoot is part of the original timeline. But what if your hard drive is fried? How would Git save you? You store your repositories on both your local machine and a remote, like GitHub or Bitbucket. Don't forget to push your changes you make to a remote with a simple "git push" command, because it's your backup... and allows you to work easily on any computer. Just pull your code with a "git pull", and start working from wherever.

Nachteile: In the pros, I oversimplified the process of using Git, because it would be impossible to explain in a short review. With how powerful Git is, complexity comes with it. It is a difficult process to become proficient with Git. I personally had to read a book and several tutorials, and even after years of use, I still feel like I'm only scratching the surface. All that is to say, it requires work to learn how to use Git. And on top of the complexity, Git is best in the command line, so if you're not comfortable in a terminal, you won't get the most out of Git.

"Git - A must for coders"

Kommentare: Git is used by almost all the organisations for code versioning. As most of the project management tools out there support integration with git, code management becomes seamless.

Vorteile: - Best versioning tool out there
- Best when multiple people are working on the same project and files
- Lot of 3rd party tools available for resolving merge issues, viewing commit diffs etc.
- Its very fast to use one you are adept at it, everything can be done command line and no need to use the interface at all

Nachteile: - Resolving merge issues can be a pain, most of the time where there are same lines of code involved auto merge never works.
- When two resources are working on different IDE for development, unless the coding styles are synchronized it creates unnecessary check-in's of formatting

"Good for version control"

Vorteile: I have been using git for version control and repository management. It is really helpful when you are working in a project that has a lot of members. Access control enables to control the level of access to specific users, which is great. Working with teams across the globe becomes easier with git.

Nachteile: Git is very extensive and sometimes it's difficult to get on-boarded with. Resolving merge conflicts is not easy and it comes with practice.

"Nice Features But Be Careful"

Kommentare: We have everything source controlled in Git now which is a huge benefit. We still need to educate or users on the complexity of Git as it was very different than our old source control.

Vorteile: Works well with other tools, i.e. VSCode.
Multiple coders working on same programs.

Nachteile: Have to be careful not when merging changes. We've had corrupt branches wipe out other people's changes.
Git commands are confusing. In our case, VS Code performs all the commands in the background. Sometimes this causes problems as users don't necessarily know what is happening.
Can't tell when someone has something 'checked out' in their own branch.

"One of the best tools to manage the versions of a digital product"

Kommentare: It is one of the best tools for managing development versions for software and bug management, change history and project evolution.

Vorteile: Very powerful tool to manage the different versions developed on a digital product in my case software, with it you can check all the changes made on the product, comment on the changes and track the changes made by the whole team so that you can always manage committed mistakes and always work with the updated work.

Nachteile: The learning curve is somewhat high for a first contact with the tool since it requires having knowledge in the use of the command terminal both CMD for windows and Linux Shell, also requires many tests to know how to work correctly in equipment or making changes on corrections or equal versions of different codes.