How Quora Balances High Code Quality with Rapid Development Speed

In software projects, code quality and development speed often seem mutually exclusive, but Quora demonstrates how to maintain high‑quality code while keeping rapid development.

Goals of Code Quality Maintenance

Quora’s engineering manager Nikhil Garg outlines four key principles:

Code should be easy to read and understand.

Different parts of the codebase should meet different quality standards.

Minimize the overhead of maintaining code quality.

Keep the codebase consistent.

Code Writing Phase

Quora built the Qlint tool for static rule checking, integrating it with editors such as Vim, Emacs, and Sublime, and tying it into the push workflow and Phabricator to provide visual feedback with minimal overhead.

Code Review Phase

Quora adopts post‑commit code review using Phabricator, allowing developers to continue work after submitting code. Reviews cover correctness, privacy, performance, architecture, reusability, and style, typically completed within 1‑2 days, with a one‑week window for flexibility. Critical code still receives pre‑commit review.

Reviewers are automatically assigned based on built‑in rules, reducing the effort for developers to find reviewers and ensuring high‑quality feedback.

Testing Phase

Quora uses a nosetests‑based framework, custom automation tools, and guidelines to lower test authoring cost. Their test servers can run the full suite in five minutes, and the “test‑local” tool runs only tests affected by recent changes, with varying coverage standards for different code changes.

Legacy Code Cleanup Phase

Quora regularly schedules cleanup weeks where dedicated teams remove obsolete code, prioritizing modules based on cleanup difficulty and future impact.

Through detailed guidelines, automation, and specialized tools, Quora has built a sustainable system that improves long‑term development speed, offering a model for other companies.