0 views collected around this technical thread.
The article explains why Google created an official Code Health Group, how it promotes readable, maintainable code through internal documentation, consulting, and tooling, and why such organized efforts often fail in other companies lacking formal support and sustained leadership.
The article presents a comprehensive framework for evaluating engineering productivity by separating efficiency (speed and quality) from effectiveness (usability), reviewing academic literature, interviewing Google engineers, and proposing four interrelated types of software quality—process, code, system, and product—along with practical measurement challenges and recommendations for technical leaders.
Measuring engineering productivity is challenging, but essential for managing and improving software processes; quantitative metrics offer scale while qualitative research provides context, and selecting meaningful metrics requires a goal‑signal‑metric framework, awareness of Goodhart’s law, and ensuring traceability to drive effective improvements.
This article presents a concise collection of ten Chinese-language resources that summarize the 2021 DORA DevOps report, the importance of consistency in R&D, fundamental efficiency principles, Microsoft’s testing shift, Google’s release and productivity metrics, and SRE health measurements, offering valuable insights for modern software engineering teams.
This article explains how GitLab uses the MR Rate metric to assess engineering productivity, outlines its definition, discusses the challenges of relying on a single metric, and presents four strategies—including improving iteration, setting KPIs, aligning OKRs, and empowering teams—to boost the MR Rate over time.
This article explains how Google, a data‑driven company, improves engineering productivity by combining a dedicated research team, the Goals‑Signals‑Metrics (GSM) framework, and the QUANTS model to create actionable, traceable metrics for code readability and other efficiency goals, while balancing quantitative and qualitative insights.
The article records Google VP Michael Bachman's 2018 talk on engineering productivity, covering the origins of EP, Google’s rebranding of QA to an Engineering Productivity team, and a detailed Q&A on rollbacks, data models, metric visualisation, tool adoption, testing strategies, static scanning, and experimentation practices.
The article explains how Google introduced the Engineering Productivity (EP) team, its evolution from QA, the organizational model across product areas, and the various metrics used to assess developer productivity, providing insight into large‑scale software engineering management.
The article shares a senior engineer’s experience transitioning a traditional QA group into an Engineering Productivity (EP) team, discussing organizational challenges, core values, role definitions, team structure, and practical strategies for improving software development efficiency in fast‑changing internet companies.