> It is not self-evident OK, how about this: any work done has non 0 probability for mistake (now we can use math to deduce the same) > You should introduce a

> It is not self-evident OK, how about this: any work done has non 0 probability for mistake (now we can use math to deduce the same) > You should introduce an external dependency into your program if and only if it provides useful extra functionality and the benefits of using it outweigh the costs. You should update an existing dependency to a new version under exactly the same conditions. People are bad in judging such stuff hence this is tautology and provide no actionable advice. > When you never need to take that action at all, for example if you include a library in your program and the library does what you need and that's that. This doesn't qualify as you already said that "you dont need to take action". I said "when waiting for action" which implies action must be done at some point.