Skip to content

Emergent Design

Status: ⏳ PENDING

The inverse of this chapter's rules — practices to recognize and avoid. Each will get a junior-level definition, a real example of the harm it causes, and the clean alternative.

Anti-Patterns to Cover

  • Speculative generality (Manager<T> for a future second use case)
  • Over-engineering for hypothetical requirements
  • YAGNI violations
  • Frameworks invented before there is a second consumer
  • Premature abstraction extracted from one example

See the chapter README for the positive rules.