[2/4] Software Engineering at Google (Do it like Google. Software development) (Category Engineering)

Continue. story About this great book, I would like to tell you a little more about the content of the book. 5 parts 25 heads

**I. Thesis (proposition)

1. What is software engineering? (What is Software Engineering?)** In this chapter, the authors explain the basic idea that software development is not a one-time job, but leads to the creation of a developing product. This means that we don’t write-once code as we used to write at Perl or now generate a conditional LLM, and we design software with changes, support and long-term viability in mind, rather than quick ad-hoc tasks. Although if you write a one-time script, it is logical to use GPT:) **II. Culture (culture)
2. How to work well on teams (How to work well in teams)** This chapter focuses on collaboration, communication and practices that enable diverse teams to work together effectively, laying the groundwork for large-scale projects. In fact, only small projects can be done alone, and if you plan something more, you will have to unite, which means software development is a team sport. To achieve success, you need to improve your soft skills:) 3. Knowledge sharing (knowledge) This chapter highlights the importance of documenting experiences and insights. It describes methods and processes to ensure the transfer of valuable knowledge. It’s funny that many people don’t like to write their own documentation, but complain about its lack or relevance. As a lover of the writing genre, I recommend such people to start with themselves and set a trend for writing documents that capture important points, for example, RFC / ADR, meeting agency, PR / FAQ from the “Working backwards” approach from Amazon. (more my review book) 4. Engineering for Equity (engineering for equality) Researches how fair processes, equal access to tools, and balanced workload distribution help maintain a productive and inclusive engineering environment. Frankly, this chapter is off the list because it seems to have been written by advocates of agenda and inclusion. 5. How to lead a team (how to lead a team) This chapter provides practical guidance on team leadership, emphasizing clear communication, aligning goals, and building trust so that teams can work best. 6. Leading at scale (leadership) It discusses issues specific to managing very large teams. The authors describe scalable management practices and structures that help maintain consistent performance and culture as teams grow. 7. Measuring engineering productivity (Measurement of Engineering Performance) This chapter focuses on informal and formal metrics to evaluate engineering performance. The authors explain how to balance speed with quality, stressing that performance is not just about results but also about performance. This topic was so interesting to me that I have been this chapter for a long time. disassemble in detail in a separate post.

#Engineering #Management #Software #Development #Processes #Leadership #SRE #DevOps