-

Week 4 – CST438 Software Engineering

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

I really enjoy reading our textbook “Software Engineering at Google.” It covers software engineering topics in detail, and it demonstrates how it is implemented in the real world by one of the biggest tech companies today. So far, we have covered the topics “What is SE?” (Software Engineering), “Testing Overview,” and “Code Reviews.” All chapters have interesting information that is relevant to the course.

From “What is SE,” I learned the difference between “software engineering” and “programming.” Programming is about producing code and software engineering is the maintenance of that code for the duration of the code’s lifespan. We must produce sustainable software which requires us to respond to changes in dependencies, technology, or product requirements.

From “Testing Overview,” I learned that testing is essential to produce quality software. It is typical for software developers to spend more time writing test code than actual program code. Another thing I found interesting about this chapter was the fact that Google used to rollback 80% of production code before it started implementing their suite of tests seriously.

In this week’s chapter, “Code Review,” I learned that code reviews are important for knowledge sharing throughout an organization. It gives you a chance to analyze code generated by your peers and learn from it as well as provide critical feedback. This chapter mentions to “Remember that you are not your code, and that this change you propose is not “yours” but the team’s. After you check that piece of code into the codebase, it is no longer yours in any case.” This part really stood out to me and gave me a new perspective when collaborating with a team and the importance of code reviews.

Comments

Post a Comment

Popular posts from this blog

-
  Week 1 – CST – 363 Introduction to Database Systems 1.       Relational database tables and spreadsheets look similar with both having rows and columns. What are some important differences between the two? Some important differences between database tables and spreadsheets are the way data is formatted and how data is stored. In a spreadsheet, every cell can store any type of data like a date, integer, or string. These data types can also have their unique format. In a database, each cell must contain only one data type helping to prevent data mismatch mistakes. In a spreadsheet, the data is stored in each cell. In a database, the data is stored in a row made up of columns. 2.       Installing and configurating a database and learning how to use it is more complicated than just reading and writing data to a file. What are some important reasons that make a database a useful investment of time? Learning how to install and c...
Read more
-
  Week 6 – CST370 – Design and Analysis of Algorithms This week we learned about AVL trees, 2-3 trees, heap, and hashing. An AVL tree is a binary search tree that has a balance factor for each node that is either 0, 1, or -1. This means that the height of a node’s left subtree minus the height of the node’s right subtree must be either 0, 1, or -1. When inserting a new node into an AVL tree, you must recheck that the balance factor of each node is still within range. If the tree is unbalanced, you must perform either right, left, double right left, or double left right rotations to balance the tree. A 2-3 tree is a tree that can have nodes that are 2-nodes or 3-nodes. A 2-node contains a single key with two children. The left child is less than the key and the right child is more than the key. A 3-node contains two ordered keys and three children. The left child is less than the two keys, the right child is more than the two keys, and the middle child is between both keys. ...
Read more
-
  CST 338 – Software Design – Wk04 Learning Journal: Markov Code Review Who did you work with? I worked with Kelia Smith. What was your strategy for solving the Markov assignment? My strategy to solve Markov was to thoroughly read the prompt first. After reading, I began by entering the fields. I then added the stubs for the methods so I can get a good idea of what I needed to do. Then I finally got down to coding while keeping the prompt open for clarification. After implementing all methods I ran the test file and revised any areas where the tests failed. I was not able to complete Markov as intended. What was THEIR strategy for solving the Markov assignment? Lia’s strategy is also to read the prompt thoroughly. She then creates a list of tasks she needs to do for the project. For Markov, she added the fields and method stubs. She then followed along with the prompt to implement each method one by one. She then ran the test file to check for errors indicated by the te...
Read more