Comment by jackblemming
1 year ago
Telling people who depended on probably internal behavior that wasn’t an explicit part of your contract to fuck off when they whine about you changing something.
1 year ago
Telling people who depended on probably internal behavior that wasn’t an explicit part of your contract to fuck off when they whine about you changing something.
When the clients have the power (e.g. a team that contributes to 90% of company's revenue), breaking the contract is often non-option from the beginning.
You don't get to decide what is and isn't an implementation detail.
And lets be real. There is no contract, and any one that is made will inevitably be broken.
That depends entirely on the economics of the situation. Like who violates the contract, and how much business they represent.
Or other measure of their importance.
Does the C library change break a major distro? Or just some obscure program with three users?
Ah yes, the “you’re holding it wrong” strategy.