Alex describes it as substituting “developer value for user value.”
The “developer experience” bait-and-switch works by appealing to the listener’s parochial interests as developers or managers, claiming supremacy in one category in order to remove others from the conversation. The swap is executed by implying that by making things better for developers, users will eventually benefit equivalently. The unstated agreement is that developers share all of the same goals with the same intensity as end users and even managers. This is not true.
Here’s the kicker, though:
By that standard, it could also stand to reason that the work we put into “design systems” falls into this trap. But there is something to be said about achieving ease of use on this front: a more consistent codebase is probably a very good thing for accessibility, UX consistency, etc. etc.
So, although I agree with Alex’s premise here, I’m not entirely sure I agree wholeheartedly on this subject.
Direct Link to Article — Permalink
The post The “Developer Experience” Bait-and-Switch appeared first on CSS-Tricks.