Kill features if they're not used. Code is so hard to maintain, it's not worth keeping it.
Conversation
Chesterton's fence or something
2
1
I guess to clarify, "kill features" must mean "remove things from the set of things you will support or fix". It does not necessarily mean change code.
2
Replying to
Yes. Leave things out to decay or be fixed by the thing you didn't realize was there. Imagine you don't know what is and isn't a test for example. Do you remove non failing tests bc you think are "unused"?
1
Obviously refactoring or renaming has a place but it is not free. Good times for me is when I want some task to run my fingers through a piece of the tech. To get it in my memory perhaps before doing something tricky.
1
Show replies

