Passive Growth
Coding Standards
Build good habits through standards and level up the team
Why Coding Standards Enable Passive Growth
Coding standards aren't just about making code style consistent — more importantly, they codify the team's best practices. When new members follow the standards, they are effectively learning the best practices the team has accumulated.
How to Implement
What Standards Cover
- Code style: Naming conventions, formatting rules, file organization
- Design principles: Component design guidelines, API design guidelines, error handling conventions
- Engineering practices: Git branching strategy, commit message conventions, PR templates
- Testing standards: Test naming, coverage requirements, mocking principles
Automated Enforcement
- Use ESLint / Prettier / StyleLint and similar tools to automatically check code style
- Configure pre-commit hooks to auto-format and check before committing
- Integrate code quality checks into the CI pipeline
- Anything that can be automated should not rely on humans to check
Iterating on Standards
- Standards aren't set in stone — review and update them regularly
- Anyone can propose changes to the standards
- When new best practices are discovered, update the standards promptly
- The purpose of standards is to improve efficiency — if a rule adds more burden than value, remove it
Documentation
- Write standards as documents and put them where they're easy to find
- Include standards as required reading during new member onboarding
- Reference standards during code review, rather than relying on personal preferences