↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

Key points to consider when doing a big software refactoring

The post argues that a big software refactoring should be treated as a structured project, with clear goals, planning, prioritization, and a defined end. It also stresses that the work affects motivation, delivery speed, and the ability to keep improving safely.

Reading notes
#

  • Set clear business goals before starting, or stakeholders may not stay committed.
  • Measure refactoring progress in a structured way, as with other project work.
  • Keep the team motivated by showing progress, planning small deliverables, and considering developer rotation.
  • Choose an approach, either improving code when touching bad parts or selecting targets proactively.
  • When goals are clear, prioritize the parts that help make those goals real.
  • When refactoring a whole codebase, use complexity and churn to decide what to tackle first.
  • Parts with high complexity and frequent change are better candidates than ugly parts that rarely need changes.
  • Treat the refactoring as a project with a beginning, middle, and end.
  • Keep good test coverage so the refactoring does not create more bugs than improvements.
  • Make sure the test suite is fast enough, because refactoring depends on running tests continuously.
  • Secure sponsor commitment, since long refactoring work can slow feature delivery for weeks or months.