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
I have noticed that many developers are reluctant to introduce explaining variables/constants.
I do, and it’s very helpful for me and my futur me and the other one.
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.
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.
Sounds like the book would be a great resource.
I’ve hopped out of electronics and now make a living coding in an adjacent area, but find myself working with colleagues that are happy approaching all tasks like a script.
Code reviews, coupling etc arent part of their vocab so in lieu of peer role models im on the look out for good resources thst aren’t just chasing the next buzzword.
