Nantilus
Software engineering at Google : lessons learned from programming over time
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 livin...
Enregistré dans:
| Auteur principal : | |
|---|---|
| Autres auteurs : | , |
| Format : | Livre |
| Langue : | anglais |
| Titre complet : | Software engineering at Google : lessons learned from programming over time / Titus Winters, Tom Manshreck, and Hyrum Wright |
| Publié : |
Sebastopol, CA :
O'Reilly Media
, 2020 |
| Description matérielle : | 1 vol. (XXV-571 p.) |
| Contenu : | Part 1. Thesis. What is software engineering?. Part 2. Culture. How to work well on teams. Knowledge sharing. Engineering for equity. How to lead a team. Leading at scale. Measuring engineering productivity. Part 3. Processes. Style guides and rules. Code review. Documentation. Testing overview. Unit testing. Test doubles. Larger testing. Deprecation. Part 4. Tools. Version control and branch management. Code search. Build systems and build philosophy. Critique: Google's code review tool. Static analysis. Dependency management. Large-scale changes. Continuous integration. Continuous delivery. Compute as a service. Part 5. Conclusion |
| Sujets : |
| LEADER | 03281cam a2200409 4500 | ||
|---|---|---|---|
| 001 | PPN249287447 | ||
| 003 | http://www.sudoc.fr/249287447 | ||
| 005 | 20201110055600.0 | ||
| 010 | |a 978-1-4920-8279-8 |b br. |d 59,99 USD ; 79,99 CAD | ||
| 035 | |a (OCoLC)1196909046 | ||
| 073 | 1 | |a 9781492082798 | |
| 100 | |a 20200923h20202020k y0frey0103 ba | ||
| 101 | 0 | |a eng | |
| 102 | |a US | ||
| 105 | |a a a 001|y | ||
| 106 | |a r | ||
| 181 | |6 z01 |c txt |2 rdacontent | ||
| 181 | 1 | |6 z01 |a i# |b xxxe## | |
| 182 | |6 z01 |c n |2 rdamedia | ||
| 182 | 1 | |6 z01 |a n | |
| 183 | 1 | |6 z01 |a nga |2 rdacarrier | |
| 200 | 1 | |a Software engineering at Google |e lessons learned from programming over time |f Titus Winters, Tom Manshreck, and Hyrum Wright | |
| 214 | 0 | |a Sebastopol, CA |c O'Reilly Media |d 2020 | |
| 215 | |a 1 vol. (XXV-571 p.) |c ill. |d 24 cm | ||
| 320 | |a Notes bibliogr. Index. | ||
| 327 | | | |a Part 1. Thesis. What is software engineering? |a Part 2. Culture. How to work well on teams |a Knowledge sharing |a Engineering for equity |a How to lead a team |a Leading at scale |a Measuring engineering productivity |a Part 3. Processes. Style guides and rules |a Code review |a Documentation |a Testing overview |a Unit testing |a Test doubles |a Larger testing |a Deprecation |a Part 4. Tools. Version control and branch management |a Code search |a Build systems and build philosophy |a Critique: Google's code review tool |a Static analysis |a Dependency management |a Large-scale changes |a Continuous integration |a Continuous delivery |a Compute as a service |a Part 5. Conclusion | |
| 330 | |a 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 time. How scale affects the viability of software practices within an engineering organization. What trade-offs a typical engineer needs to make when evaluating design and development decisions. |2 4e de couverture | ||
| 606 | |3 PPN02788547X |a Logiciels |x Essais |2 rameau | ||
| 606 | |3 PPN136844030 |a Google Apps (logiciels) |2 rameau | ||
| 606 | |3 PPN142421618 |a Google Web Toolkit (environnement de développement d'applications) |2 rameau | ||
| 700 | 1 | |3 PPN250240238 |a Winters |b Titus |4 070 | |
| 702 | 1 | |3 PPN250240696 |a Manshreck |b Tom |4 070 | |
| 702 | 1 | |3 PPN250241056 |a Wright |b Hyrum |4 070 | |
| 801 | 3 | |a FR |b Abes |c 20201109 |g AFNOR | |
| 979 | |a SCI | ||
| 930 | |5 441092104:67843087X |b 441092104 |j u | ||
| 998 | |a 878049 | ||