2 ms·
It means that as time passes by, the things that need to be done accumulate and hence the pain of doing them. You don't need evidence for that. Its a common sen
by Silhouette 6y ago
It means that as time passes by, the things that need to be done accumulate and hence the pain of doing them. You don't need evidence for that. Its a common sense.
I couldn't disagree more. It is not self-evident either that updates will inevitably need to be done or that the pain of doing them if they are needed will increase (never mind increase exponentially, as the article arbitrarily claimed) with time.
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.
Otherwise, give one example when waiting for action (and in absence of divine/external intervention) makes it easier.
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.
- majkinetor 6y ago> 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.