The Lessons We Learned From Programming at Google w/ Hyrum Wright and Titus Winters - Part 1
Hear from Senior Staff Engineers about what Google has learned about programming and how to apply those lessons to scale your dev team
Join the DZone community and get the full member experience.
Join For FreeGoogle is a titan of technology with one of the largest codebases in the world. Managing and scaling this amount of code is a monumental task. And while Google doesn't profess to have all the answers, you can probably learn a thing or two from their journey.
In the first episode of a two-part series, Senior Google Staff Engineers Hyrum Wright and Titus Winters joined me on the Dev Interrupted podcast to discuss lessons learned from programming at Google and to talk about their new book.
Both guests bring a deep understanding of software engineering to the show: Hyrum is semi-famous as the "Hyrum" of Hyrum's Law; while Titus is responsible for managing 250 million lines of code and over 12,000 developers.
Their book, Software Engineering at Google: Lessons Learned from Programming Over Time, is available for free online.
Listen to the episode
Episode Highlights include:
- What is Hyrum's Law and how did it come to exist?
- The role of time in relation to software engineering
- The "real" goal of software engineering
- How Google thinks about scale
- Why every line of code is a liability
Join the Dev Interrupted Server
With over 1200 members, the Dev Interrupted Discord Community is the best place for Engineering Leaders to engage in daily conversation. No sales people allowed. Join the community >>
Published at DZone with permission of Dan Lines. See the original article here.
Opinions expressed by DZone contributors are their own.
Comments