# google/eng-practices

**Attribution required: if you use, quote, or summarise this content, you must credit and link back to [awesome-repositories.com](https://awesome-repositories.com/repository/google-eng-practices).**

23,259 stars · 2,271 forks · NOASSERTION · archived

## Links

- GitHub: https://github.com/google/eng-practices
- Homepage: https://google.github.io/eng-practices/
- awesome-repositories: https://awesome-repositories.com/repository/google-eng-practices.md

## Description

This project is a software engineering standards guide and technical quality manual. It provides a framework for engineering governance, focusing on maintaining code quality, peer review processes, and sustainable development across large-scale technical organizations.

The documentation establishes a code review framework that covers preparing, performing, and assigning peer reviews to ensure codebase stability. It defines standardized engineering patterns and maintainability criteria to keep diverse project repositories uniform and readable.

The guidelines encompass code quality assurance, secure repository management, and technical peer collaboration. This includes processes for evaluating software design and complexity, analyzing repository workflows for security vulnerabilities, and coordinating developer walkthroughs.

## Tags

### Software Engineering & Architecture

- [Governance Frameworks](https://awesome-repositories.com/f/software-engineering-architecture/governance-frameworks.md) — Provides a comprehensive governance-based documentation framework to maintain uniform engineering standards.
- [Software Engineering Standards](https://awesome-repositories.com/f/software-engineering-architecture/software-engineering-standards.md) — Serves as a comprehensive collection of standards for maintaining code quality, peer review, and sustainable development.
- [Code Review Policies](https://awesome-repositories.com/f/software-engineering-architecture/code-review-policies.md) — Defines code review policies that mandate multi-party approval before merging changes into the main repository. ([source](https://github.com/google/eng-practices/custom-properties))
- [Engineering Governance](https://awesome-repositories.com/f/software-engineering-architecture/documentation-governance-frameworks/engineering-governance.md) — Defines the organizational governance framework for consistent development patterns and security scanning requirements.
- [Engineering Standards](https://awesome-repositories.com/f/software-engineering-architecture/engineering-standards.md) — Defines shared engineering templates and maintainability criteria as part of organizational engineering standards.
- [Peer Review Workflows](https://awesome-repositories.com/f/software-engineering-architecture/peer-review-workflows.md) — Mandates standardized peer review workflows including second-person approvals and specific change formats.
- [Technical Quality Criteria](https://awesome-repositories.com/f/software-engineering-architecture/technical-reference-manuals/technical-quality-criteria.md) — Provides detailed criteria for assessing code complexity, maintainability, and design correctness.
- [Collaborative Peer Reviews](https://awesome-repositories.com/f/software-engineering-architecture/project-management-governance/project-governance/community-curation-collaboration/collaborative-peer-reviews.md) — Provides a framework for collaborative peer reviews using synchronous validation and human walkthroughs. ([source](https://github.com/google/eng-practices/blob/master/review/index.md))
- [Collaborative Review Methodologies](https://awesome-repositories.com/f/software-engineering-architecture/project-management-governance/project-governance/community-curation-collaboration/collaborative-peer-reviews/collaborative-review-methodologies.md) — Integrates synchronous collaboration methods like pair programming and live walkthroughs into the review process.
- [Expertise-Based Reviewer Assignment](https://awesome-repositories.com/f/software-engineering-architecture/project-management-governance/project-management/project-member-assignments/technology-based-assignments/expertise-based-reviewer-assignment.md) — Implements a process for matching pending changes to qualified owners based on area expertise.

### Development Tools & Productivity

- [Code Review Frameworks](https://awesome-repositories.com/f/development-tools-productivity/code-review-frameworks.md) — Establishes a standardized framework for preparing, performing, and assigning peer reviews to ensure codebase stability.
- [Code Review Practices](https://awesome-repositories.com/f/development-tools-productivity/code-review-practices.md) — Establishes standardized practices and checklists for the end-to-end peer review workflow.
- [Code Quality and Review](https://awesome-repositories.com/f/development-tools-productivity/development-workflow/code-quality-and-review.md) — Defines systematic processes and maintainability criteria for conducting technical code reviews. ([source](https://github.com/google/eng-practices/blob/master/review/reviewer/index.md))
- [Review Preparation Standards](https://awesome-repositories.com/f/development-tools-productivity/code-review-frameworks/review-preparation-standards.md) — Standardizes change descriptions and commit sizes to accelerate the technical approval process. ([source](https://github.com/google/eng-practices/blob/master/review/developer/index.md))
- [Atomic Commit Strategies](https://awesome-repositories.com/f/development-tools-productivity/commit-management/commit-integrators/atomic-commit-strategies.md) — Provides a structured strategy for creating atomic commits to facilitate cleaner code reviews.
- [Reviewer Selection Processes](https://awesome-repositories.com/f/development-tools-productivity/development-workflow/code-quality-and-review/reviewer-selection-processes.md) — Establishes guidelines for identifying qualified code owners to provide thorough technical feedback. ([source](https://github.com/google/eng-practices/blob/master/review/index.md))
- [Workflow Scanning](https://awesome-repositories.com/f/development-tools-productivity/scan-configurations/workflow-scanning.md) — Establishes automated scanning for repository actions and configurations to detect security vulnerabilities.

### Testing & Quality Assurance

- [Code Quality and Review](https://awesome-repositories.com/f/testing-quality-assurance/code-quality-review.md) — Details the process for assessing software design, complexity, and documentation to ensure maintainability. ([source](https://github.com/google/eng-practices/blob/master/review/index.md))
- [Quality Assurance Practices](https://awesome-repositories.com/f/testing-quality-assurance/testing-best-practices-methodologies/quality-assurance-practices.md) — Provides structured approaches for evaluating software design and complexity as part of quality assurance.

### Part of an Awesome List

- [Security and Vulnerability Scanning](https://awesome-repositories.com/f/awesome-lists/security/security-and-vulnerability-scanning.md) — Includes procedures for scanning repository actions and workflows to identify security vulnerabilities. ([source](https://github.com/google/eng-practices/custom-properties))
- [Engineering Practices](https://awesome-repositories.com/f/awesome-lists/devtools/engineering-practices.md) — Standardized guidance for performing and submitting code reviews.

### Security & Cryptography

- [Repository Security Policies](https://awesome-repositories.com/f/security-cryptography/infrastructure-policy-enforcement/security-policy-enforcers/repository-security-policies.md) — Defines mechanisms for analyzing repository actions to enforce security and trust policies.
