![Software Engineering at Google](/assets/artwork/1x1-42817eea7ade52607a760cbee00d1495.gif)
![Software Engineering at Google](/assets/artwork/1x1-42817eea7ade52607a760cbee00d1495.gif)
![](/assets/artwork/1x1-42817eea7ade52607a760cbee00d1495.gif)
![](/assets/artwork/1x1-42817eea7ade52607a760cbee00d1495.gif)
Software Engineering at Google
Lessons Learned from Programming Over Time
-
-
3.7 • 3 Ratings
-
-
- $49.99
-
- $49.99
Publisher Description
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 timeHow scale affects the viability of software practices within an engineering organizationWhat trade-offs a typical engineer needs to make when evaluating design and development decisions