17 docs tagged with "refactoring"

TL;DR

Manage large refactorings and migrations through feature flags and abstraction layers.

Track code health with cyclomatic complexity, coupling metrics, and technical debt; implement refactoring strategies and automate code quality gates in CI/CD.

Safely migrate data between systems using dual writes, backfill, and change data capture.

Break apart monolithic systems along domain boundaries while maintaining consistency.

High-level modules should not depend on low-level modules; both should depend on abstractions. Invert the dependency flow.

Master DRY principle: eliminate knowledge duplication for maintainable code, improved consistency, and reduced bugs.

Strategies for refactoring and improving domain models as understanding deepens

One class doing too much with many responsibilities, violating single responsibility principle.

Execute database schema changes without downtime using multi-phase rollouts.

Assign responsibility to the class that has the information needed to fulfill it

Clients should not depend on interfaces they don't use. Break large interfaces into smaller, focused ones.

Master the Principle of Least Knowledge to reduce coupling and improve maintainability in complex systems.

Wrap legacy systems with facades and anti-corruption layers to reduce their impact.

Subtypes must be substitutable for their supertypes without breaking client code. Preserve behavioral contracts.

Complex, tangled control flow without clear structure, making code hard to understand and modify.

Incrementally replace legacy systems by growing new functionality alongside the old.