A code review is a process where someone other than the author(s) of a piece of code examines that code. At Google we use code review…

First, it’s important to remember why we’re bothering with pull requests and code reviews in the first place.

Accept that many programming decisions are opinions. Discuss tradeoffs, which you prefer, and reach a resolution quickly.

These guidelines stem from what code review should accomplish. It’s impossible for us to lay out guidelines which will be applicable to every…

Correction of Error (COE) is a scalable, repeatable process designed to enable organizations…

On [date], we noticed the air temperature levels in both the X°C and Y°C chillers began to rise.

Clear documentation is key to an effective incident postmortem process. Many teams use a comprehensive template to collect…

Shakespeare Search down for 66 minutes during period of very high interest in Shakespeare due to discovery of a new sonnet.

This page is intended to be reviewed during a post-mortem meeting that should be scheduled within 5 business days of any event.

HashiCorp is a remote-first company, meaning we optimize our workflows for decentralized remote teams.

We want to restrict what users can do inside of the product, so that people can't accidentally modify global...

A healthy engineering organization demands a culture of asking for and welcoming feedback on our work.

Rename this RFC in this format: RFC <number> <status>: <title> This is a starting point for an RFC...

Delete notes in italics. Remove sections that are not applicable. Primary author(s): who owns this document and should be contacted about it?

Indent using 4 spaces. No tabs. Avoid starting methods with an empty line. There should not be a need to use multiple consecutive…