Software engineering at Google

• Verfasst von: Winters, Titus [VerfasserIn]
• Verfasst von: Manshreck, Tom [VerfasserIn]
• Verfasst von: Wright, Hyrum [VerfasserIn]
• Titel: Software engineering at Google
• Titelzusatz: lessons learned from programming over time
• Verf.angabe: Titus Winters, Tom Manshreck, and Hyrum Wright
• Ausgabe: [First edition].
• Verlagsort: [Place of publication not identified]
• Verlag: Ascent Audio
• Jahr: 2021
• Umfang: 1 online resource (1 audio file (23 hr., 35 min.))
• Fussnoten: Online resource; title from title details screen (O'Reilly, viewed February 28, 2023)
• ISBN: 978-1-6637-2859-3
• ISBN: 1-6637-2859-3
• Datenträger: Online-Ressource
• Sprache: eng
• Sach-SW: Audiobooks
• K10plus-PPN: 1840139242
• K10plus-PPN:
  Universitätsbibliothek
• Lokale URL UB: Zum Volltext
• Lokale URL UB: Bibliothek der Medizinischen Fakultät Mannheim der Universität Heidelberg
• Bibliothek/Idn: UW / m4297411393
• Lokale URL Inst.: Zum Volltext

Abstract

Today, software engineers need to know not only how to program effectively but also how to develop proper engineering practices to make their codebase sustainable and healthy. This book emphasizes this difference between programming and software engineering. How can software engineers manage a living codebase that evolves and responds to changing requirements and demands over the length of its life? Based on their experience at Google, software engineers Titus Winters and Hyrum Wright, along with technical writer Tom Manshreck, present a candid and insightful look at how some of the world's leading practitioners construct and maintain software. This book covers Google's unique engineering culture, processes, and tools and how these aspects contribute to the effectiveness of an engineering organization. You'll explore three fundamental principles that software organizations should keep in mind when designing, architecting, writing, and maintaining code: How time affects the sustainability of software and how to make your code resilient over time How scale affects the viability of software practices within an engineering organization What trade-offs a typical engineer needs to make when evaluating design and development decisions.