HjemGrupperSnakMereZeitgeist
Søg På Websted
På dette site bruger vi cookies til at levere vores ydelser, forbedre performance, til analyseformål, og (hvis brugeren ikke er logget ind) til reklamer. Ved at bruge LibraryThing anerkender du at have læst og forstået vores vilkår og betingelser inklusive vores politik for håndtering af brugeroplysninger. Din brug af dette site og dets ydelser er underlagt disse vilkår og betingelser.

Resultater fra Google Bøger

Klik på en miniature for at gå til Google Books

Software Engineering at Google: Lessons…
Indlæser...

Software Engineering at Google: Lessons Learned from Programming Over Time (udgave 2020)

af Titus Winters (Forfatter), Tom Manshreck (Forfatter), Hyrum Wright (Forfatter)

MedlemmerAnmeldelserPopularitetGennemsnitlig vurderingSamtaler
935296,590 (4.17)Ingen
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… (mere)
Medlem:gottfried_leibniz
Titel:Software Engineering at Google: Lessons Learned from Programming Over Time
Forfattere:Titus Winters (Forfatter)
Andre forfattere:Tom Manshreck (Forfatter), Hyrum Wright (Forfatter)
Info:O'Reilly Media (2020), Edition: 1, 602 pages
Samlinger:Dit bibliotek
Vurdering:
Nøgleord:to-read, computer-science

Værk information

Software Engineering at Google: Lessons Learned from Programming Over Time af Titus Winters

Ingen
Indlæser...

Bliv medlem af LibraryThing for at finde ud af, om du vil kunne lide denne bog.

Der er ingen diskussionstråde på Snak om denne bog.

Viser 5 af 5
This book covers a wide variety of Software Engineering concepts. A software engineer's job is not just to write code and deploy, they should also think about scaling, cost - Capex, Opex, resource etc.

We've faced the ill-effects of Hyrum's law and learned our lesson from it. For e.g,. I prefer descriptive field names though that'll lead to longer character length.

"Everything your organization has to do repeatedly should be scalable in terms of human effort." ( )
  nmarun | Dec 10, 2023 |
Book concentrates on Software Engineering, not on Programming - it rarely discusses code itself, but challenges in supporting large engineering environment, where code may live for 10 or more years and has to be modified by many different teams.

Really recommended, if you want to "peek behind the curtain" a bit and see how big companies work, and how their scale poses unique challenges. ( )
  064 | May 26, 2022 |
Woo, are these folks full of themselves or what. As a software engineering guide iit is okay, though questions of size are not honestly addressed. As a study of the sociology of a tech monopoly, it is fascinating. ( )
  jcvogan1 | Mar 31, 2022 |
Horrendously uneven collection of essays. Some valuable discussion but inexplicably bundled together with the most worthless waffle the likes of which you'd have to go to reddit to read. ( )
  Paul_S | Jul 4, 2021 |
Relatively little is known about how to organize/manage software projects so that they come to a successful, on-time resolution that lasts the test of experience. This is the field of software engineering, and over the last two decades, Google has mastered this art. They share their hard-wrought wisdom in this book.

Many developers, like me, wish they could undertake several internships at leading companies like Apple, Google, Microsoft, or Facebook. They could learn the tricks of the trade from what made these entities so successful. Concerning Google, software developers now can just consult this book. It provides an in-depth look into the state of the art at this engineering company. Each chapter is written by company experts and covers 25 timely topics ranging from code testing to dependency management, from continual integration to cloud services.

Google is one of only a few companies that have broached these issues in depth ever. They do not claim that their answers will solve all problems for all time. Rather, they encourage readers to learn from their well-reasoned thoughts and understand their own problems in that light. This book is relevant to the start-up as well as the corporate developer. For us computer programmers, this book is fodder and inspiration for continually producing better software.

I find the quality of writing particularly fresh. Instead of hiding behind older and well-established verbiage, they provide newly thought-out terminology in newly explained reasonings. For a technical book, this work is extremely engaging. The reader rarely if ever gets the sense that the authors are merely regurgitating rehashed theory.

This book is particularly relevant to software developers and managers of software efforts. It gives a lingua franca to the software development effort and provides abstracted concepts that will help companies move development forward. All the way to the end, I stayed engaged, and I predict many others will, too. Kudos to Google for giving back to the industry in this way! ( )
  scottjpearson | Oct 8, 2020 |
Viser 5 af 5
ingen anmeldelser | tilføj en anmeldelse
Du bliver nødt til at logge ind for at redigere data i Almen Viden.
For mere hjælp se Almen Viden hjælpesiden.
Kanonisk titel
Originaltitel
Alternative titler
Oprindelig udgivelsesdato
Personer/Figurer
Vigtige steder
Vigtige begivenheder
Beslægtede film
Indskrift
Tilegnelse
Første ord
Citater
Sidste ord
Oplysning om flertydighed
Forlagets redaktører
Bagsidecitater
Originalsprog
Canonical DDC/MDS
Canonical LCC

Henvisninger til dette værk andre steder.

Wikipedia på engelsk

Ingen

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

Ingen biblioteksbeskrivelser fundet.

Beskrivelse af bogen
Haiku-resume

Aktuelle diskussioner

Ingen

Populære omslag

Quick Links

Vurdering

Gennemsnit: (4.17)
0.5
1
1.5
2
2.5
3 1
3.5
4 3
4.5
5 2

Er det dig?

Bliv LibraryThing-forfatter.

 

Om | Kontakt | LibraryThing.com | Brugerbetingelser/Håndtering af brugeroplysninger | Hjælp/FAQs | Blog | Butik | APIs | TinyCat | Efterladte biblioteker | Tidlige Anmeldere | Almen Viden | 208,716,748 bøger! | Topbjælke: Altid synlig