convention-yagni

To minimize software scope, apply the YAGNI principle by implementing only explicitly requested features and deferring speculative enhancements until a proven need emerges. This reduces system complexity and maintenance overhead.

The YAGNI principle in software engineering stands for "You Aren't Gonna Need It," warning against implementing features before they are required. It helps teams reduce risk, dependencies, and unnecessary work by keeping systems small and focused.

Reduce API technical debt and dependencies by enforcing scope constraints that defer speculative work until needed. This encourages simple, maintainable solutions and minimizes unnecessary enhancements before concrete demand emerges.

Avoid premature optimization and generic plugin architecture when there is no concrete demand. Deferring speculative work until a proven need emerges keeps systems small, reduces risk, and minimizes unnecessary maintenance overhead.

Deferring features until needed helps with project planning by minimizing unnecessary work and reducing risk. It enforces scope constraints, ensuring teams build only what is explicitly requested for simple, maintainable solutions.

The best way to keep software systems small and focused is to implement only currently requested features and skip speculative enhancements. This minimizes scope, reduces dependencies, and lowers maintenance overhead.