A UX design tool has one job: Materialize the designer's intent as working code. Everything the tool does is in service of refining that intent (ideation, exploration, validation). A programing tool has one job: Materialize the user's intent as working code. UX design tools are programming tools. UX tools today care very little for code. But they should, and it needs to be at their core.

id also make the argument that programming tools do very little in the opposite direction—they're much worse at communicating intent. and they're obviously visually weak

@Garth Goldwater Trying to fix that 😊 See https://futureofcoding.slack.com/archives/CCL5VVBAN/p1659007210210439 on how we're able to let designers communicate their intent by visually editing code. Working UI code, that uses real production components, is a much more precise way for designers to communicate their intent than compared to having their developer counterparts inspect their Figma/Sketch/XD vector-graphics files.

oh yeah—i think i saved that gif lol