Software Engineering at Google • Titus Winters & Matt Kulukundis • GOTO 2022

Cool. interview Titus Winters, co-curator of the bookSoftware Engineering at Google"with Matt Kulukundis at the Goto Conference Book Club. I have this book in line to read, and almost in first place.

If you go back to the interview, the guys discuss the following cool questions:

• Build systems Importance of Building System to Improve Productivity
• Build systems dependencies - about dependencies in assembly and why it should be hermetic and repeatable
• What is Google trying to improve in engineering? - DORA (DevOps Research and Assessment) The need for technical managers to set goals to improve CDs within their projects (But often technical managers do not work with their hands much, so they do not see joints in the pipeline working with the code of their teams and delivering them to production.)
• Cheat sheet for building great teams The importance of a culture where everyone is involved and kind to each other. Details are in project by Aristotle
• Where can Google improve on from a culture’s perspective? - about chapters in the book that focus on leadership, such as the importance of asking "simple" questions so that everyone understands what the discussion is about
• How to grow as a software developer? It's about decision-making and the right to make mistakes, and that's how people grow -- making decisions and taking responsibility for them. But here it is important that the team has the right culture and psychological safety, the main factor of the successful team from the project Aristotle mentioned above.
• What chapter is missing entirely in the book? There were three potential chapters that were not included in the book. About app frameworks that help write code, abstracting from the complexity of details and using DI (dependency inversion) About working with issues (And then the authors honestly said that they just didn't have any ideas that there's something interesting to say here, but maybe someone can cover this topic philosophically ... but apparently not in Google.) Design, but this is the subject of a separate book.
• What decisions are hard to undo? - about interfaces, versioning and serialization formats:)
• Book recommendations During the presentation there were recommendations of books, both scientific and fantastic: -- Titus Winters, Tom Manshreck & Hyrum Wright • Software Engineering at Google -- Forsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOps -- George Fairbanks • Just Enough Software Architecture --Fred Brooks Jr. • The Mythical Man-Month -- Kim Scott • Just Work -- Douglas R. Hofstadter • Gödel, Escher, Bach -- Douglas R. Hofstadter • I Am a Strange Loop -- Alasdair MacIntyre • After Virtue -- N. K. Jemisin • The Fifth Season -- Becky Chambers • Wayfarers Series -- Ken Liu • The Dandelion Dynasty -- David Farley • Modern Software Engineering -- Martin Kleppmann • Designing Data-Intensive Applications -- Zhamak Dehghani • Data Mesh

#Engineering #SystemDesign #Management #Leadership #Software #SoftwareDevelopment