3 ms·
Oh no, I always get rid of stuff I don't know why it's there. Because if it does not break when I run "make check", it's not covered by the testing and it shoul
by Joky 11y ago
Oh no, I always get rid of stuff I don't know why it's there.
Because if it does not break when I run "make check", it's not covered by the testing and it shouldn't have been there in the first place anyway.
And if it had a use for someone, but nobody knows, removing it is also a very efficient way to figure out :)
- deleted 11y ago[deleted]
- logn 11y agoThis all depends on the nature of the business, the app, codebase, customers, processes of dev/QA/ops, etc. For example, this cavalier attitude might work at a social media startup but not at a bank.