kramme:elegant-refactor

Refactoring hacky code involves a deliberate four-step process: extract learnings from the quick implementation, identify the inelegance, design an elegant solution, and reimplement while verifying equivalence to prevent regressions.

You should refactor a quick fix when the hacky implementation is complete, functional, and merits improvement. Validate that the fix exists and works before applying the refactor workflow to ensure the elegant replacement maintains behavioral equivalence.

Document code changes by extracting learnings from the original hacky fix before designing the elegant solution. This captures the context of the quick implementation, preventing future regressions and maintaining code quality.

Verify code equivalence by validating that the elegant solution produces the same functional results as the original hacky fix. The workflow requires confirming the initial fix is complete before replacing it to prevent future regressions.

Refactoring hacky code into an elegant solution requires no external dependencies. The workflow is a self-contained process for improving code maintainability and best practices without relying on additional software libraries.