Skip to content

stevenacoffman/software-design

v0.1.0MIT

Software design and refactoring: deep modules, information hiding, and incremental change.

fowler-opportunistic-refactoring

Use when deciding when and why to refactor during normal work: preparatory (code isn't shaped for a new feature), comprehension (code is hard to follow), litter-pickup (problems found in passing), or long-term structural fixes over weeks.

Read SKILL.md at the source

Pinned to revision e4081cbb4d29, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.