Description 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.
As a direct result of helping to build out refactoring tooling and automation, Titus has encountered first-hand a huge swath of the shortcuts that engineers and program.
Along the way he has started several Google projects that believed to be in the top 10 largest refactorings in human history.
For the last 7 years, Titus and his teams have been organizing, maintaining, and evolving the foundational components of Google\'s C++ codebase using modern automation and tooling.
At Google, he is the library lead for Google\'s C++ codebase: 250 million lines of code that will be edited by 12K distinct engineers in a month.
Today, he is the chair of the global subcommittee for the design of the C++ standard library.
By emphasizing three fundamental principles that Software organizations should keep in mind when designing, architecting, and writing code, this book explains: Fundamental differences between Software Engineering and Programming The Software Engineering lifecycle from code development to testing to deprecation How to effectively manage your codebase and efficiently respond to change Why culture is important, and how processes, practices, and tools come into play Tradeoffs: how an organization makes optimal Software decisions by keeping Time and scale in mind About the Author Titus Winters is a Senior Staff Software Engineer at Google, where he has worked since 2010.
Most teaching on this subject concentrates on programming, but little on Software engineering.
At Google, Software Engineering represents roughly 80-90% of the work, while only 10-20% of the Time involves original programming.
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.
Description 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
