CST 438 Week 4

WELCOME TO WEEK 4

Learning Journal - CST 438

What is the most interesting thing you have learned in your reading of "Software Engineering at Google"?

    What stood out to me the most from this chapter was how Google sees code review as more than just making sure the code works. It’s really about whether the code can be understood and maintained later on. I didn’t realize before how much they focus on making sure code will still make sense to other people in the future, especially as teams grow or change. The part that said code is a liability really changed how I think about adding new features. 
    Writing code isn’t always progress if it just adds more work for someone else down the line. I also thought it was interesting how greenfield reviews are handled. They’re not just about checking the code but also making sure it follows an approved design and is fully tested. That made me see how important it is to plan ahead before even writing anything. Overall, this chapter made me think differently about how much thought and care goes into keeping a codebase healthy over time.

Comments

Post a Comment

Popular posts from this blog

CST 370 Week 3

Image
  WELCOME TO WEEK 3 Learning Journal - CST 370  This week, we learned a lot. We started with Brute-Force String Matching , an algorithm that aligns the pattern against the first characters of the text and begins to match pairs of characters from left to right. It continues this process until there is either a match or, in the worst case, the pattern is not found in the text at all. The best case occurs when the first characters in the text immediately match the pattern. Next, we learned about Exhaustive Search and its application to three important problems. Exhaustive Search is simply a brute-force approach to combinatorial problems such as permutations, combinations, and subsets of a given set. The first problem we covered was the Traveling Salesman Problem , which involves finding the shortest path through a set of cities (visiting each city exactly once) and returning to the starting city. It is also described as the problem of finding the shortest Hamiltonian cycle. The...
Read more

CST 438 Week 7

Image
  WELCOME TO WEEK 7 Learning Journal - CST 438 Describe some of the differences between using an Agile process and using a  Plan and Document (or Waterfall) process.        This week I reviewed the differences between using an Agile process and a Plan and Document (Waterfall) process. In a Plan and Document approach, requirements are written as a detailed SRS during a dedicated requirements phase, with the expectation that they remain complete and stable for the rest of the project. Changes are handled through a formal change control process, which involves evaluating the impact on cost and schedule before updating documents, code, and tests. Design is completed after requirements and is intended to be stable, while cost estimates are based on person-weeks from past experience. Scheduling uses tools like PERT charts with periodic status meetings, and testing is split between developers writing unit tests and QA handling system and acceptance tests. Howeve...
Read more

CST 311 Week 1

Image
  WELCOME TO WEEK 1 Learning Journal This week has been really good so far. I learned a lot of new things that I found very interesting. To begin with, this week's chapter started with an introduction to what the internet is and how it is viewed. It is first described as the "nuts and bolts," where it talks about all the hardware and software that is involved. For example, there are billions of computing devices such as hosts (or end systems) running network applications. Hosts can be a PC, server, laptop, smartphone, etc. In order to carry signals across from one end system to another, there are communication links such as wired or wireless links. There are also intermediate devices called packet switches, which forward packets. There are also protocols that control the sending and receiving of messages sent from one end system to another. Some examples of these protocols are TCP and IP. Protocols are used to define the format and order of the messages that are being sen...
Read more