CST438 Week 3
This week was all about Git and source code version control. Here are the main takeaways.
What I Learned
Git keeps a full history of every change made to a project through commits. This makes it easy to roll back to a working state if something breaks. Branching lets multiple developers work on separate features at the same time without interfering with each other, and pull requests add a layer of code review before anything touches the main branch.
The distributed workflow we practiced, clone a repo, create a dev branch, push changes, open a pull request, merge into main, is the same flow I use at Keasy so this week felt very natural.
What Git Does Not Solve
The most interesting part of the lab was the warning that a successful merge does not mean the code works. Two developers can edit different lines, merge with zero conflicts, and still break the program. If one developer renames a variable and another references the old name in a different part of the file, Git sees no conflict but the code no longer compiles. Git only understands text, not logic. This is why having a solid test suite matters so much after every merge.
Takeaway
Git is a powerful tool but it is only one layer of quality control. Testing still has to do the rest.
Comments
Post a Comment