What is the most interesting thing you have learned in your reading of "Software Engineering at Google"?
I found it particularly interesting to read about how Google’s initial push towards testing was difficult. The book mentions a specific statistic, that early on at Google, nearly 80% of production pushes contained bugs that had to be rolled back. With that number in mind, it is no wonder that testing became an integral part of Google’s development cycle.
Another interesting topic that has been detailed in the book is the many different types of tests. If I were to take away one idea from what I have read so far, I would say that writing and maintaining complex systems, especially in a collaborative environment, is a wholly difficult task. The amount of automation needed to define these systems, and to prevent them succumbing to unintended regressions or alterations, can be staggering.
No comments:
Post a Comment