Skip to main content

Week 80

-

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

    The most interesting thing I learned from Software Engineering at Google is how important code reviews are beyond just finding bugs. I didn't realize that code reviews also aim to improve code readability, encourage knowledge sharing, and create a historical record of why changes were made. Something else I found interesting is that Google aims to keep code reviews small, around 200 lines when possible. This is to make it easier to review and speed up development. I sort of just assumed that code reviews would be exponentially larger because these are seasoned, experienced programmers, and I thought that Google would have such drastic changes at a time. It showed me that code reviews are as much about collaboration and maintainability as they are about catching mistakes.

Comments

Post a Comment

Popular posts from this blog

Week 32

-
 Wow... It really is the last week of CST 334. I vividly remember the week when we went through and downloaded Docker. Using PowerShell and terminal seemed like something straight out of a movie, but learning low-level stuff like that is key to success as a computer scientist. The PA codes were also a hurdle to get accustomed to. Coding tasks are always daunting, but doing it in C was even more of a pain. But once again, languages where you're in charge of memory allocation are very important and equally important to learn. Over the course, we learned about processes and how you manage them. We had a lot of emphasis on memory virtualization, and then we had the midterm. Then, concurrency and persistence. And as I'm writing this, I'm preparing for the upcoming final exam. As for the final exam, I will try to be more cognizant of the time. On the previous midterm, I had been surprised by the time, as I thought I had more. I did all the big questions to realize I only had 12 m...
Read more

Week 58

-
 This week was a little rough because I had so much work. I am still in the process of tackling it, but I figured I'd get this out of the way. I even got called in on my day off, but we push. AVL, 2-3, and max heap trees are all new to me. But it was nice to see something pop up from my Data Structures & Algorithms course from back in the day. Hashing, it's probably my favorite data structure. I think it's super neat and unique. Handling collisions is also fun. I was so stumped on the puzzle this week, but then again,n I always am. After this class engagement, it's straight to the programming assignment for me.
Read more

Week 54

-
 It's been a little over 1 year since I started my journey at Monterey Bay, which is crazy to think about.  This week, we learned about a lot of stuff, including notations for algorithm analysis, definitions of time efficiency notations, nonrecursive algorithms, and more. One thing that stumped me a lot during the readings was the understanding of the difference and how to remember the difference between big O, theta, and omega. I had to use ChatGPT to break the concepts down a lot and explain any misconceptions I had/ reinforce any ideas I got right. For the first time, I got one of the puzzles on my own, the 4-gallon puzzle, which wasn't too bad. I almost got the racing one down, but I said 6 instead of 7, forgetting about the other cars from group A.
Read more