3 ms·
Developer Experience I suppose
by DaGardner 5y ago
Developer Experience I suppose
- kleiba 5y agoOh man, I'm getting too old for this shit...
- marton78 5y agoIt's like UX but for developers...
- TeMPOraL 5y agoWhich makes no sense if the developers are the users... But in the spirit of "there are only two business models - bundling and unbundling", I guess there are only two marketing tricks: use an old term for a new thing, and introduce a new term for an old thing...
- zeroxfe 5y agoOr more charitably, while the UX/DX distinction isn't very meaningful for this project, there are lots of products (e.g., payments) that target both (non-developer) end users and developers. It helps to be able to separate the personas.
- TeMPOraL 5y agoI don't think this holds. As the rule goes, there are only three cardinal numbers: zero, one, many. What are the chances you product has only two meaningful personas - "users" and "developers"? Take that payment system. People who buy things are obviously users, people who write CMS plugins for that system are obviously developers. But what about, say, analysts studying reports from that system? Accountants making sure the money flows where it should? Sysadmins keeping the backend components running? These are all users too. Where UX makes sense as a broad concept, giving a separate acronym to one small subset of potential users... doesn't make sense.
- zeroxfe 5y agoIt's perfectly reasonable (and quite common) to have acronyms for your major personas, and generic terminology for the tail.