Software Engineering at Google: Lessons Learned from Programming Over Time 1st Edition, Kindle Edition

4.3 out of 5 stars 21 ratings
Flip to back Flip to front
Audible Sample Playing... Paused   You are listening to a sample of the Audible narration for this Kindle book.
Learn more
ISBN-13: 978-1492082798
ISBN-10: 1492082791
Why is ISBN important?
ISBN
This bar-code number lets you verify that you're getting exactly the right version or edition of a book. The 13-digit and 10-digit formats both work.
Scan an ISBN with your phone
Use the Amazon App to scan ISBNs and compare prices.
Kindle App Ad
<Embed>
Buy
$36.79
Digital List Price: $50.99

Deliver to your Kindle or other device


Buy for others

Give as a gift or purchase for a team or group.Learn more

Buying and sending eBooks to others


Select quantity
Buy and send eBooks
Recipients can read on any device

Additional gift options are available when buying one eBook at a time.  Learn more


These ebooks can only be redeemed by recipients in the US. Redemption links and eBooks cannot be resold.

Quantity: 
This item has a maximum order quantity limit.
See all formats and editions Hide other formats and editions
Price
New from Used from
Kindle
$36.79

The Amazon Book Review
The Amazon Book Review
Book recommendations, author interviews, editors' picks, and more. Read it now
click to open popover

Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
    Apple
  • Android
    Android
  • Windows Phone
    Windows Phone
  • Click here to download from Amazon appstore
    Android

To get the free app, enter your mobile phone number.

kcpAppSendButton
Amazon Business : For business-only pricing, quantity discounts and FREE Shipping. Register a free business account

From the Publisher

“Software engineering,” however, sounds more serious, as if it implies the application of some theoretical knowledge to build something real and precise. Mechanical engineers, civil engineers, aeronautical engineers, and those in other engineering disciplines all practice engineering. They all work in the real world and use the application of their theoretical knowledge to create something real. Software engineers also create “something real,” though it is less tangible than the things other engineers create.

Unlike those more established engineering professions, current software engineering theory or practice is not nearly as rigorous. Aeronautical engineers must follow rigid guidelines and practices, because errors in their calculations can cause real damage; programming, on the whole, has traditionally not followed such rigorous practices. But, as software becomes more integrated into our lives, we must adopt and rely on more rigorous engineering methods. We hope this book helps others see a path toward more reliable software practices.

What This Book Isn’t

This book is not meant to cover software design, a discipline that requires its own book (and for which much content already exists). Although there is some code in this book for illustrative purposes, the principles are language neutral, and there is little actual “programming” advice within these chapters. As a result, this text doesn’t cover many important issues in software development: project management, API design, security hardening, internationalization, user interface frameworks, or other language-specific concerns. Their omission in this book does not imply their lack of importance. Instead, we choose not to cover them here knowing that we could not provide the treatment they deserve. We have tried to make the discussions in this book more about engineering and less about programming.

Editorial Reviews

About the Author

Titus Winters is a Senior Staff Software Engineer at Google, where he has worked since 2010. Today, he is the chair of the global subcommittee for the design of the C++ standard library. 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. 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. Along the way he has started several Google projects that believed to be in the top 10 largest refactorings in human history. 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 programmers may take to “just get something working”. That unique scale and perspective has informed all of his thinking on the care and feeding of software systems.

Tom Manshreck is a Staff Technical Writer within Software Engineering at Google since 2005, responsible for developing and maintaining many of Google's core programming guides in infrastructure and language. Since 2011, he has been a member of Google's C++ Library Team, developing Google's C++ documentation set, launching (with Titus Winters) Google's C++ training classes, and documenting Abseil, Google's open source C++ code. Tom holds a BS in Political Science and a BS in History from the Massachusetts Institute of Technology. Before Google, Tom worked as a Managing Editor at Pearson/Prentice Hall and various startups.

Hyrum K. Wright is a Staff Software Engineer at Google, where he has worked since 2012, mainly in the areas of large-scale maintenance of Google's C++ codebase. Hyrum has made more individual edits to Google's codebase than any other engineer in the history of the company. He is a member of the Apache Software and an occasional visiting faculty member at Carnegie Mellon University. Hyrum received a PhD in Software Engineering from the University of Texas at Austin, and also holds an MS from the University of Texas and a BS from Brigham Young University. He is an active speaker at conferences and contributor to the academic literature on software maintenance and evolution.

--This text refers to the paperback edition.

Product details

Customer reviews

4.3 out of 5 stars
4.3 out of 5
21 customer ratings
How does Amazon calculate star ratings?
Reviewed in the United States on April 20, 2020
Verified Purchase
12 people found this helpful
Comment Report abuse
Reviewed in the United States on June 2, 2020
Verified Purchase
review imagereview imagereview image
4 people found this helpful
Comment Report abuse
Reviewed in the United States on May 15, 2020
Verified Purchase
One person found this helpful
Comment Report abuse
Reviewed in the United States on June 21, 2020
Verified Purchase
One person found this helpful
Comment Report abuse
Reviewed in the United States on June 5, 2020
Verified Purchase
2 people found this helpful
Comment Report abuse
Reviewed in the United States on May 21, 2020
Verified Purchase
2 people found this helpful
Comment Report abuse

Top international reviews

Paris Apostolopoulos
4.0 out of 5 stars Interesting read + easy to read
Reviewed in the United Kingdom on April 29, 2020
Verified Purchase
2 people found this helpful
Sending feedback...
Thank you for your feedback.
Report abuse
Angad Nadkarni
3.0 out of 5 stars Very cool, but likely not indispensable
Reviewed in India on April 3, 2020
Verified Purchase
Sending feedback...
Thank you for your feedback.
Report abuse
test
5.0 out of 5 stars A great and useful book
Reviewed in Germany on May 2, 2020
Verified Purchase
Sending feedback...
Thank you for your feedback.
Report abuse
Adev
5.0 out of 5 stars instructive, applied, complete.
Reviewed in France on April 14, 2020
Verified Purchase
Sending feedback...
Thank you for your feedback.
Report abuse