cst 438: week 4

In Chapter 9 of Software Engineering at Google, one thing that stood out to me was how code reviews are not just about catching bugs, but about making sure the code stays readable and maintainable over time. I used to think reviews were mainly for checking if the code works, but this chapter showed that they are more about ensuring anyone on the team can understand and modify the code later. I also found it interesting that Google has specific roles like code owners and readability reviewers, which makes the process more structured. The emphasis on small, frequent changes instead of large ones also makes a lot of sense because it makes reviews easier and more effective. Overall, it helped me see code reviews as an important part of building scalable and collaborative software, and it's not just a final step before merging code.