5 ms·
Exactly. It'll break sometime (it's software). So when do you want it to break? And is the benefit of controlling/planning the timing of that breakage worth the
by mooreds 3y ago
Exactly. It'll break sometime (it's software). So when do you want it to break? And is the benefit of controlling/planning the timing of that breakage worth the cost of operating the software?
As always, it depends. Questions I'd ask:
* How critical is the software to your application's proper functioning?
* How big is the team?
* Who are your customers and what are customer expectations around your application's proper functioning?
* How often does the library change?
* What expectations does a service set around backwards compatibility? What commitments are made?