CST438 Week 4

This week's reading from Software Engineering at Google was about code reviews. The part that stuck with me most was how Google splits the review across three roles: peer engineer, code base owner, and language readability approver. Each one is looking at the code differently, and that structure makes the whole process more intentional than what I'm used to.

What Stood Out

The bug fix review point was the most interesting. It's not enough to verify the fix works. The reviewer is also supposed to ask why the existing tests didn't catch the bug in the first place. That's a much higher bar, and a more useful one.

Takeaway

Reading about the code base owner role, someone asking whether the team can actually maintain this code if the original author leaves, made me realize that question doesn't get asked enough in most places.

Comments

Post a Comment

Popular posts from this blog

CST363 Week 4 May 21st - May 27th

Five things i've learned so far in the course so far... 1. Relational Schema Design and Normalization How to structure data into tables, define their primary and foreign keys, and apply normalization rules to eliminate redundancy and ensure data integrity. 2. Basic CRUD operations with SQL Writing SELECT , INSERT , UPDATE , and DELETE statements to retrieve and manipulate data, including filtering with WHERE , sorting with ORDER BY , and limiting results with LIMIT 3. Joins and Set Operations Combining data across multiple tables using INNER JOIN , LEFT/RIGHT JOIN , as well as operations like UNION and EXCEPT to merge or compare result sets. 4. Aggregate Functions and Grouping Using COUNT() , SUM() , AVG() , MIN() , MAX() along with GROUP BY and HAVING clauses to summarize statistics and filter groups. 5. Database Design Designing databases by creating ER diagrams using primary and foreign key relationships between entities. Three questions I have regarding databases... 1. Scali...
Read more

CST363 Week 3 May 14th - May 20th

A view is essentially a saved query that you can treat like a table. Under the hood, the database doesn’t necessarily store the view’s data separately; it re-runs the defining SELECT every time you reference it  The similarities to a table are the Rows and Column, you SELECT from a view similar as to how you would do it from a table. Join and filters also looks the same. The key differences between the two... Aspect Tables View Storage Physically stores data on disk. Usually virtual (query results are generated on the fly). Some DBs support materialized views. Primary Key Defined directly on the table; enforced. No inherent PK—though some systems allow unique indexes on views, most treat them as keyless. Updatability Always updatable (barring triggers/locks). Only if certain rules are met: Comparing SQL with Java there are notable differences a...
Read more

CST489 Week 9

What project milestones did you accomplish this week? This week I successfully completed the AWS Cloud Practitioner course on Amazon as well as the Agile Project Management course . In addition to completing the coursework, I applied the AWS concepts I learned by deploying an older project to the cloud in order to test and reinforce my new skills. The site is currently being hosted at: http://54.177.87.154:3000/ For this project, I built and deployed the application using several AWS services. I created a Docker image of my project and stored it in Amazon ECR (Elastic Container Registry) . My ECS service pulls this image and runs the containerized application. The project’s data is stored in an Amazon RDS MySQL database , which handles the backend data storage. I also configured an S3 bucket to store static assets such as pet photos, CSS files, and JavaScript files. Additionally, I set up security groups to control network traffic and manage access to the different services. The g...
Read more