Software Engineering at Google: Lessons Learned from Programming Over Time

Software Engineering at Google: Lessons Learned from Programming Over Time

<div><p>How do you 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 K. 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.</p><p>At Google, software engineering represents roughly 80-90% of the work, while only 10-20% of the time involves original programming. Most teaching on this subject concentrates on programming, but little on software engineering. By emphasizing three fundamental principles that software organizations should keep in mind when designing, architecting, and writing code, this book explains:</p><ul><li>Fundamental differences between software engineering and programming</li><li>The software engineering lifecycle from code development to testing to deprecation</li><li>How to effectively manage your codebase and efficiently respond to change</li><li>Why culture is important, and how processes, practices, and tools come into play</li><li>Tradeoffs: how an organization makes optimal software decisions by keeping time and scale in mind</li></ul></div>