For developers, the four extensive chapters on testing should alone be worth the entry price. I would very highly recommend SEaG to any engineering leader trying to improve her team's game. Even if you are working nowhere near Google scale, the book covers a lot of fundamentals, especially on how to sustainably develop software and make objective trade-offs while doing so. It also offers a treasure of insights and ideas from how Google made a billion lines of code change at one time, or how its automated tests could successfully process 50,000 change requests a day, or how Google Production System is perhaps one of the best machines humans ever engineered. The book disambiguates “programming” from “engineering”, and walks through the hardest engineering challenge - how to scale. Not targeting on algorithm, language, tools or libraries, it focuses on “Software Engineering” as a system, i.e., stuff that is not taught at any school. The writers are deeply knowledgable, passionate about their crafts and offer insight after insight into topics ranging from human psychology to the flaws of over-embracing mock testing. Very rarely I give a 5-star rating to a technical book, but SEaG is completely worth the two weeks I immersed myself into learning Culture, Processes and Tools of Google Software Teams. Collectively, these five books, “Top N” Google Tech Talks (check YouTube) and - depending on your role - coding best practices (check their site) are collectively a combination of top notch combined technical and business education in itself. Thank you! Many places do many things exceptionally well - but the earnestness to coach and educate others is an extreme rarity - a version of Survivorship Bias - among the “Big Techs”. Executives should read “How Google Works” by Eric Schmidt on - “how Google works ”!įirst, It is admirable how the company wants to spread its hard-earned wisdom. Security Engineers should buy the very recent “Building Secure and Reliable Systems” on “how Google implements defense”. Senior org leaders should minimally read the first part (Culture) pairing with “Work Rules” (Laszlo bock on “how Google leads”). Systems engineers should pair this book with “Site Reliability Engineering” (from Google) on “how Google runs infra”. This book is about “how Google runs code”. Google has open sourced "how" they do everything. Para obtener más información sobre cómo y para qué fines Amazon utiliza la información personal (como el historial de pedidos de Amazon Store), visita nuestro Aviso de privacidad. Para ello, visita Preferencias de cookies, tal y como se describe en el Aviso de cookies. Puedes cambiar de opinión en cualquier momento. Haz clic en “Personalizar cookies” para rechazar estas cookies, tomar decisiones más detalladas u obtener más información. Estos terceros utilizan cookies para mostrar y medir anuncios personalizados, generar información sobre la audiencia, y desarrollar y mejorar los productos. Esto incluye el uso de cookies propias y de terceros que almacenan o acceden a información estándar del dispositivo, como un identificador único. Si estás de acuerdo, también utilizaremos las cookies para complementar tu experiencia de compra en las tiendas de Amazon, tal y como se describe en nuestro Aviso de cookies. También utilizamos estas cookies para entender cómo utilizan los clientes nuestros servicios (por ejemplo, mediante la medición de las visitas al sitio web) con el fin de poder realizar mejoras. Utilizamos cookies y herramientas similares que son necesarias para permitirte comprar, mejorar tus experiencias de compra y proporcionar nuestros servicios, según se detalla en nuestro Aviso de cookies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |