jdelafargue

> I do agree that familiarity with the tech stack is very useful, but beyond that I’d argue its best to let those focus on what they do best.

+1

> I'm actually building a tool right now that aims to solve this problem. I partially agree with your statement. Yes, designers need to learn how to interact with a UI component, but I don't think they should go so far as coding.

I agree with this. UX design and programming are skillsets that are sufficiently complex/different that the key is to allow each discipline to have the tools to _understand_ and interact with the other really well, but not to expect all designers to become programmers or vice-versa.

Maybe :) TBD!

That does sound useful! Yeah I now realise the title is ambiguous :S

Cheers Omar! Looking forward to your feedback :)

<3 Hope all is well with you!

Thanks! Standups looks great but we're currently non-remote :)

Got it, thanks for clarifying!

Thanks for the feedback! Really helpful

I agree with you and to be honest this is something we get picked up on often when talking to people outside the (UX) design world... we're just so used to people using the term like that in our space that we forget!

> imho quality/easy docs are the difference between loving a job and burnout!

That's a great quote :)

As in front-end engineering? Or software _architecture_ design? If you mean front-end then this is already something we enable as we have integrations with front-end coding tools like Storybook and have plans to build on that :)

Thank you :)

Thanks for your support! :)

Yep that's actually something we want to do in the future: giving design/front-end better continuous integration/testing tools such as diff-checking and visual regression testing