The book “Tidy First?” introduces the concept of “tidyings,” which are small refactorings that don’t change program behavior, but make it easier to implement behavioral changes. It’s important to structurally prepare code before implementing behavioral changes. A balance must be struck between the time value of money and optionality in software, highlighting the need to create a structure that supports quick changes.
I stole the summary from https://tldr.tech/webdev
Neat post. I’m too lazy to read the book, so I appreciate the summary.
I like the taxonomy of refactorings. It’s always helpful to have names for things.