R&D Management 5 min read

Curated Collection of Google and Microsoft Engineering Practices and Resources

This article presents a curated list of ten insightful resources covering Google’s OKR guide, code coverage best practices, code health principles, software product team efficiency metrics, unit testing responsibilities, quality assurance case studies, effective code review, Microsoft’s testing transformation, agile misconceptions, and related engineering topics.

Continuous Delivery 2.0
Continuous Delivery 2.0
Continuous Delivery 2.0
Curated Collection of Google and Microsoft Engineering Practices and Resources

1. Google OKR Guide – A concise overview of how Google uses OKRs internally, highlighting six common pitfalls and offering eight quiz questions to validate the effectiveness of your own OKRs.

2. Code Coverage Best Practices – Google’s Authoritative Recommendation – Summarizes twelve key viewpoints from Google’s fifteen‑year experience with automated testing, emphasizing the importance of overall coverage, cultural impact, and integration/system test coverage.

3. Google Code Health Guide (Part 1) – Part of a series discussing Google’s attitude toward code, what makes code easy to understand, how good API design prevents misuse, and why primitive types should not be over‑emphasized.

4. Measuring Software Product Team Effectiveness – Provides a comprehensive map of product team efficiency metrics, drawing from the book “Continuous Delivery 2.0” and two years of practical experience.

5. What Counts as Unit Tests? Who Should Write Them? – Google & Microsoft Perspectives – Explains the simple answers both companies arrived at after years of transformation.

6. Case Study: How Google and Facebook Ensure Quality – Discusses the trade‑off between bug impact on a small app versus massive platforms, highlighting the scale of effort required for high‑impact bugs.

7. How to Conduct Efficient Code Reviews – Answers seven key questions to improve code‑review standards, foster healthy feedback culture, and provide objective evidence of engineering skills.

8. Microsoft’s Testing Transformation Journey (5,000‑word article) – Describes how Microsoft awakened its testing organization, tackled common transformation challenges, and regained a leading position.

9. Opinions on the Realities of Agile – Reflects on why agile, despite a decade of popularity in China, still feels “naked” and under‑delivered.

10. Microsoft Admits Mistakes in Software Testing – Acknowledges that commercial success masked methodological flaws, prompting a reassessment of testing practices.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

testingSoftware EngineeringCode reviewGoogleMicrosoftOKR
Continuous Delivery 2.0
Written by

Continuous Delivery 2.0

Tech and case studies on organizational management, team management, and engineering efficiency

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.