Google's infamous internal 2010 “I just want to serve 5TB” video now public (youtube.com)

Article summary

The article discusses a 2010 internal Google video that led to changes in the company's internal tools and operations. The video's influence is still debated among former and current Google employees. The discussion revolves around Google's readability process, which aims to ensure code quality and consistency. The process has been influential in shaping the company's coding practices.

Main themes

• Google's readability process
• code quality and consistency
• automated vs human code review
• development velocity and gatekeeping
• coding style and best practices
• scalability and company size

What commenters say

• Google's readability process has improved code quality and consistency, but may be overly bureaucratic and restrictive.
• The process has been effective in training engineers to write high-quality code, but its benefits may not outweigh the costs.
• Automated tools are insufficient for ensuring code readability, and human judgment is necessary for evaluating code quality.
• The readability process may stifle development velocity and create unnecessary gatekeeping, particularly for new engineers or those working on unfamiliar codebases.
• Consistency in coding style is more important than personal preference, and a codified set of best practices can help achieve this consistency.
• The readability process may be too focused on style over substance, and can lead to unnecessary debates over minor issues.
• Google's size and complexity require a more formalized process for ensuring code quality, but this process may not be suitable for smaller companies or more agile development environments.