4 ms·
Analyzing what impact removing a piece of software has is typically harder than thinking about what my addition does. This is especially true for libraries wher
by heisenbit 5y ago
Analyzing what impact removing a piece of software has is typically harder than thinking about what my addition does. This is especially true for libraries where it is hard to know exactly where and why something may have been used. Removal might require significant re-testing while addition may allow to get away with targeted testing. Cleaning up code may be the right thing to do if one knows what one is doing but some system are too big of complex that you can only pray you know what you are doing.
- aszen 5y agowhat kind of language are u using, using a statically typed functional language most removal of code is self obvious and even automated. u remove a method, it tells u to remove this and this too.