How Quora Balances High Code Quality with Rapid Development

In software projects, code quality and development speed often appear mutually exclusive, but Quora demonstrates that both can be achieved through disciplined engineering practices.

Code Quality Maintenance Goals

Quora’s engineering manager outlines four key principles: code should be readable, different parts may follow different quality standards, maintenance overhead should be minimized, and the codebase must stay consistent.

Code Writing Stage

Quora built the static‑analysis tool Qlint, which enforces style and quality rules across languages, integrates with editors such as Vim, Emacs, and Sublime, and ties into the push workflow and Phabricator, providing low‑overhead feedback that improves consistency.

Code Review Stage

The team adopts post‑commit reviews using Phabricator, allowing developers to continue work after pushing code; reviews cover correctness, privacy, performance, architecture, reusability, and style, typically completed within 1‑2 days, with automatic reviewer assignment based on built‑in rules.

Testing Stage

Quora created a nosetests‑based testing framework, auxiliary automation tools, and a “test‑local” utility that runs only tests affected by recent changes, enabling the entire test suite to finish in about five minutes while applying varied coverage criteria per change type.

Legacy Code Cleanup Stage

Regular “cleanup weeks” are organized to remove obsolete code, with dedicated teams or company‑wide participation; modules are prioritized based on cleanup difficulty and future impact.

Through detailed guidelines, automated tooling, and well‑structured processes, Quora achieves a sustainable balance of rapid development and long‑term code quality, offering a model for other organizations.