CST438 - Module 4

What did I learn in the fourth week of CST438?  

One of the most interesting things from the reading "Software Engineering at Google" is that a code review isn't a single gate, but three gates of approval. Basically, it requires a 'looks good to me' response from a peer reviewer, sign-off from a code base owner, and approval from someone who has an understanding of the language. These three gates can be held by a singular person or split and assigned to different people, which is dependent on who is making the change through a pull request. A tech lead who owns the code and has an understanding of the language can simply merge it with a 'looks good to me' response, while an intern would require all three roles to be satisfied before merging to main. Furthermore, through this review system that decomposes distinct concerns into correctness, maintainability, ownership, and style, it makes it so that the main (production) is never altered with code that doesn't fit to certain constraints depicted within the repository.

As for what else we did this week other than read, was do assignment two, which was resolving some functions and implementing UnitTests. The only issue that came up during the whole organization project was view iteration organization and the pull requests. Nevertheless, everything turned out fine for the most part and we are heading towards the third iteration of the project.