3 ms·
Thinking about it some more, conservative users are also a factor. If we change anything, we impose additional cost on our customers, which have to retest, rede
by js8 10y ago
Thinking about it some more, conservative users are also a factor. If we change anything, we impose additional cost on our customers, which have to retest, redeploy and retrain. So it's not easy for this reason alone.
When you have a platform for internal use only (or a platform that is available free of charge without any warranties), you can decide to make a change by fiat.
We would like to "move fast and break things", but our customers unfortunately don't appreciate that sentiment.
- vog 10y agoThinking even more about it, many changes are "cosmetic", such as renaming fields or restructuring essentially flat structures. These may make the system more consistent and easier to understand for newcomers, but break old code for "no reason". So developers should develop some kind of taste to distinguish between "real" changes and "cosmetic" changes.