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
Yeah my own code is greek and latin to me if I come back a few months later. Excessing logger statements and descriptive variable/function names save my bacon more than I can admit.