Skip to main content

Posts

Featured

CST438 - Module 3

What did I learn in the third week of CST438? Working through lab 5 and setting up the GitHub organization and project for assignment 1, showcased how much Git can organize a team workflow. Basically, branches allow developers to isolate code to do work independently from main, making it so that any changes don't apply to main and can be merged through a pull request, which allows for a code review before a merge process is initiated. For example, during the two-developer simulation in lab 5, two branches working on the same file were to be merged, the first branch was successful, while the second branch wasn't and required a refactor to resolve merging issues, showcasing local repositories on their own machine, independent commits, code review, and syncing when they are pushed/merged into main, showing real VCS. Furthermore, merge conflicts are very straightforward to resolve, and can be shown through a code review that specifies approval or required actions that can then be r...

Latest Posts

CST438 - Module 2

CST438 - Module 1

CST383 - Module 8

CST383 - Module 7

CST383 - Module 6

CST383 - Module 5

CST383 - Module 4

CST383 - Module 3

CST383 - Module 2

CST383 - Module 1