3 ms·
The opposite problem is much more common and shouldn't be downplayed: A developer or designer using the "every change breaks someone's workflow" exaggeration as
by happytoexplain 2y ago
The opposite problem is much more common and shouldn't be downplayed: A developer or designer using the "every change breaks someone's workflow" exaggeration as an excuse to break a workflow.
- maaaaattttt 2y agoor (worse?) to not change anything; but I think this comes usually more from devs (guilty as charged).
- JohnFen 2y agoThis. The fact that any change to software people are used to using will bring pain to the users shouldn't mean that devs automatically prefer or avoid breaking workflows. What it should do is encourage actually thinking about the cost/benefit (to the user) of the change. Users will accept the pain that change brings if the benefits of that change outweigh the cost of it. If the cost/benefit ratio isn't favorable to the user, they will, quite understandably, resent the change.
- Netch 2y agoMost cases an initial estimate of change cost is utterly overstated because emotional and reluctant to change. (And, well, this fact is also abused by wreckers who explain any reasonable objection with this factor;))
- BiteCode_dev 2y ago"We don't break userspace"
- renox 2y agoUnfortunately this is an exception not the rule..