CST 438 Week 3

Question: Describe what are the good points about using Git for source code management.  What are possible problems that Git merge does not solve when merging code from different developers?

 

Using Git for source code management has a lot of good points that make working on projects easier. One of the biggest benefits is how simple it is to keep track of changes. Every time someone updates the code, Git records it, so you can always go back and see what happened or undo something if needed. It also makes it easier to update the codebase because everyone can pull the latest version and stay in sync.

Another good point is how Git supports teamwork. Developers can work on different tasks in separate branches without stepping on each other’s work. It also helps track progress because you can see who worked on what and when. Even though Git is mainly a command‑line tool, many GUIs make it easier to understand what’s going on, especially for beginners.

But Git doesn’t solve everything. Even if a merge goes through with no conflict, that doesn’t mean the code will actually work. For example, two developers might change different parts of the project, and Git won’t detect a conflict because the lines don’t overlap. But once the code runs, one change might break the other. Git can only detect text‑based conflicts, not logical or functional ones. So even after a clean merge, bugs can still show up.

Overall, Git is great for organizing and managing code, but it can’t replace communication between developers or proper testing. Those are still needed to catch problems that Git can’t see.