Bookbot

Software Engineering at Google

Lessons Learned from Programming Over Time

Parametry

  • 602 strony
  • 22 godziny czytania

Więcej o książce

The approach to and understanding of software engineering at Google is unlike any other company. With this book, you'll get a candid and insightful look at how software is constructed and maintained by some of the world's leading practitioners. Titus Winters, Tom Manshreck, and Hyrum K. Wright, software engineers and a technical writer at Google, reframe how software engineering is practiced and taught: from an emphasis on programming to an emphasis on software engineering, which roughly translates to programming over time. You'll learn: Fundamental differences between software engineering and programming How an organization effectively manages a living codebase and efficiently responds to inevitable change Why culture (and recognizing it) is important, and how processes, practices, and tools come into play

Zakup książki

Software Engineering at Google, Hyrum Wright, Titus Winters, Tom Manshreck

Język
Rok wydania
2020
Oprawa
(miękka),
Stan książki
Dobry
Cena
55,47 zł

Metody płatności

Nikt jeszcze nie ocenił.Oceń

Tytuł
Software Engineering at Google
Podtytuł
Lessons Learned from Programming Over Time
Język
angielski
Rok wydania
2020
Oprawa
miękka
Liczba stron
602
ISBN10
1492082791
ISBN13
9781492082798
Seria
Opis
The approach to and understanding of software engineering at Google is unlike any other company. With this book, you'll get a candid and insightful look at how software is constructed and maintained by some of the world's leading practitioners. Titus Winters, Tom Manshreck, and Hyrum K. Wright, software engineers and a technical writer at Google, reframe how software engineering is practiced and taught: from an emphasis on programming to an emphasis on software engineering, which roughly translates to programming over time. You'll learn: Fundamental differences between software engineering and programming How an organization effectively manages a living codebase and efficiently responds to inevitable change Why culture (and recognizing it) is important, and how processes, practices, and tools come into play