Software engineering at Google : lessons learned from programming over time / Titus Winters, Tom Manshreck, and Hyrum Wright

By:

Winters, Titus [VerfasserIn]

Contributor(s):

Resource type: Ressourcentyp: Buch (Online)Book (Online)Language: English Publisher: Beijing ; Boston ; Farnham ; Sebastopol ; Tokyo : O'Reilly, February 2020Edition: First editionDescription: 1 Online-Ressource (609 pages)ISBN:

9781492082767

Subject(s):

Additional physical formats: 9781492082798. | Erscheint auch als: Software engineering at Google. Druck-Ausgabe First edition. Beijing : O'Reilly, 2020. xxv, 571 SeitenDDC classification:

005.1

RVK: RVK: ST 230Local classification: Lokale Notation: inf 3.70LOC classification:

QA76.758

Online resources:

Summary: Example: Distributed Builds -- Example: Deciding Between Time and Scale -- Revisiting Decisions, Making Mistakes -- Software Engineering Versus Programming -- Conclusion -- TL -- DRs -- II. Culture -- 2. How to Work Well on Teams -- Help Me Hide My Code -- The Genius Myth -- Hiding Considered Harmful -- Early Detection -- The Bus Factor -- Pace of Progress -- In Short, Don't Hide -- It's All About the Team -- The Three Pillars of Social Interaction -- Why Do These Pillars Matter? -- Humility, Respect, and Trust in Practice -- Lose the ego -- Learn to give and take criticismSummary: Fail fast and iterate -- Blameless Post-Mortem Culture -- Learn patience -- Be open to influence -- Being Googley -- Conclusion -- TL -- DRs -- 3. Knowledge Sharing -- Challenges to Learning -- Philosophy -- Setting the Stage: Psychological Safety -- Mentorship -- Psychological Safety in Large Groups -- Growing Your Knowledge -- Ask Questions -- Understand Context -- Scaling Your Questions: Ask the Community -- Group Chats -- Mailing Lists -- YAQS: Question-and-Answer Platform -- Scaling Your Knowledge: You Always Have Something to Teach -- Office Hours -- Tech Talks and Classes -- DocumentationSummary: Intro -- Foreword -- Preface -- Programming Over Time -- Google's Perspective -- What This Book Isn't -- Parting Remarks -- Conventions Used in This Book -- O'Reilly Online Learning -- How to Contact Us -- Acknowledgments -- I. Thesis -- 1. What Is Software Engineering? -- Time and Change -- Hyrum's Law -- Example: Hash Ordering -- Why Not Just Aim for "Nothing Changes"? -- Scale and Efficiency -- Policies That Don't Scale -- Policies That Scale Well -- Example: Compiler Upgrade -- Shifting Left -- Trade-offs and Costs -- Example: Markers -- Inputs to Decision MakingSummary: Understanding the Need for Diversity -- Building Multicultural Capacity -- Making Diversity Actionable -- Reject Singular Approaches -- Challenge Established Processes -- Values Versus Outcomes -- Stay Curious, Push Forward -- Conclusion -- TL -- DRs -- 5. How to Lead a Team -- Managers and Tech Leads (and Both) -- The Engineering Manager -- The Tech Lead -- The Tech Lead Manager -- Moving from an Individual Contributor Role to a Leadership Role -- The Only Thing to Fear Is ... Well, Everything -- Servant Leadership -- The Engineering Manager -- Manager Is a Four-Letter WordSummary: Updating documentation -- Creating documentation -- Promoting documentation -- Code -- Scaling Your Organization's Knowledge -- Cultivating a Knowledge-Sharing Culture -- Respect -- Incentives and recognition -- Establishing Canonical Sources of Information -- Developer guides -- go/ links -- Codelabs -- Static analysis -- Staying in the Loop -- Newsletters -- Communities -- Readability: Standardized Mentorship Through Code Review -- What Is the Readability Process? -- Why Have This Process? -- Conclusion -- TL -- DRs -- 4. Engineering for Equity -- Bias Is the DefaultPPN: PPN: 1697745059Package identifier: Produktsigel: ZDB-4-NLEBK

Holdings ( 0 )

No physical items for this record