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
if you read his writings, gk chesterton was quite clear in insisting that his fence concept must never be applied to software. it should all be torn down without a second thought
1
2
Just going to edit the live running code that controls the life support system k brb
2
1
okay so if you're not running a life support system it should be fine
And the changing a wheel on a moving bus analogy doesn't fit at all with software that you can test and fractionally release
You can never test really in "write" systems i.e. no redo. You just release. Consider trading systems, NASA.
Another good one is support beams/structure in an old mine shaft. You want to "cleanup". What is risk of "adding" safety structure vs delete? It's constant assessment.
1
Totally different in analytics and non critical stuff. Especially things that are supposed to give understanding. These can and should be cleaned up rewritten often I think.
2
1
Show replies