My concern with this is that the discussion revolves around effects and not causes. If we're unable to meet on a common ground then we're unable to work together to evaluate solutions.
Certainly things are changing, and it sounds like some UX engineers weren't in the loop on that. No one sane is discounting the importance of UX. I've seen a surge in interest in design systems lately and I consider that the industry's response to a need for restructuring. That might not be good enough, we'll see.
UX engineers are in the loop, they just don't agree with the direction things are going. That's a valid position, and not a statement of ignorance.
That said, the picture isn't all bleak. I'd say if JS frameworks are able to adequately meet important accessibility concerns, there's not really a huge problem. Until that's addressed, though, especially in a way that accounts for the lack of expertise of new developers juxtaposed with the required cognitive load of these technologies, then it is a pretty big problem.
Poor choice of words. "Out of the loop" meaning UX dev concerns weren't impactful in the larger conversation's process.
Material Design Components for the Web has done an amazing job with accessibility, but unfortunately development progress has lagged significantly behind framework-specific libraries like MaterialUI, Vuetify, etc.
I haven't worked with Storybook so can't speak to the developer experience, but that was one of the first solutions for a new front-end engineering framework workflow. I've gotten up close with Vue Design System, which isn't too bad. I'd like to hear about other' solutions and their experiences with them.
I would too! Navigating the wealth of tech out there isn't easy; I'm sure there are better solutions that just the one's I've heard about. That's a big reason why I'd like this to be a broader conversation.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My concern with this is that the discussion revolves around effects and not causes. If we're unable to meet on a common ground then we're unable to work together to evaluate solutions.
Certainly things are changing, and it sounds like some UX engineers weren't in the loop on that. No one sane is discounting the importance of UX. I've seen a surge in interest in design systems lately and I consider that the industry's response to a need for restructuring. That might not be good enough, we'll see.
UX engineers are in the loop, they just don't agree with the direction things are going. That's a valid position, and not a statement of ignorance.
That said, the picture isn't all bleak. I'd say if JS frameworks are able to adequately meet important accessibility concerns, there's not really a huge problem. Until that's addressed, though, especially in a way that accounts for the lack of expertise of new developers juxtaposed with the required cognitive load of these technologies, then it is a pretty big problem.
Poor choice of words. "Out of the loop" meaning UX dev concerns weren't impactful in the larger conversation's process.
Material Design Components for the Web has done an amazing job with accessibility, but unfortunately development progress has lagged significantly behind framework-specific libraries like MaterialUI, Vuetify, etc.
I haven't worked with Storybook so can't speak to the developer experience, but that was one of the first solutions for a new front-end engineering framework workflow. I've gotten up close with Vue Design System, which isn't too bad. I'd like to hear about other' solutions and their experiences with them.
I would too! Navigating the wealth of tech out there isn't easy; I'm sure there are better solutions that just the one's I've heard about. That's a big reason why I'd like this to be a broader conversation.