Engineering Standards

3. Code Quality Standards

• DRY (Don't Repeat Yourself): But avoid "Premature Abstraction". Two instances of duplication are okay; three require a shared utility.
• KISS (Keep It Simple, Stupid): Favor readable code over "clever" one-liners.
• SOLID: Apply where it adds clarity, especially Dependency Inversion for testability.

4. Continuous Refactoring

• Boy Scout Rule: Always leave the code slightly cleaner than you found it.
• Small Commits: Refactor in separate commits from feature work to make reviews easier.

Verification Checklist

• Tech debt is documented and prioritized.
• Critical paths have high test coverage (>90%).
• Code follows the team's style guide and architectural patterns.
• Dependencies are audited for security and obsolescence.
• Large files/components are broken down into smaller, focused units.