At work I have deprecated many older software components in favor of implementing newer, less painful to maintain ones.
That's great, but know that you're optimizing your QoL over the users'. If and when that new shiny thing becomes an objective improvement of the user experience, only then will users share your joy of switching to something easier to maintain. Just don't expect, or even worse, force users to switch just because it makes life easier for you.
I also wouldn't tell someone not to use an existing component that works, unless I have a concrete recommendation for a better alternative.
Yes, this is key. And precisely what the person in TFA is failing to do. UX >>> DX, always.
I work on embedded systems that are rarely user facing, so ease of maintenance tends to directly improve the customer's experience for the overall system.
Comments
That's great, but know that you're optimizing your QoL over the users'. If and when that new shiny thing becomes an objective improvement of the user experience, only then will users share your joy of switching to something easier to maintain. Just don't expect, or even worse, force users to switch just because it makes life easier for you.
Yes, this is key. And precisely what the person in TFA is failing to do. UX >>> DX, always.
I work on embedded systems that are rarely user facing, so ease of maintenance tends to directly improve the customer's experience for the overall system.