Skip to main content
bash TV

The Design-Code Roundtrip That Isn't — Jonathan Gordon, ReWeaver AI

AI Engineer

1.3K views10 Sept 2026

YouTube

Jonathan Gordon was deep in a vibe coding session, ignoring the wall of text scrolling past, when the phrase innerHTML caught his eye. He knew it as an injection risk, stopped the agent, and made it revert. That was the moment he started reading the code again. Gordon has spent more than thirty years building developer tools and IDEs, and he defines his title precisely: a design code roundtrip is a full loop both ways with no loss of fidelity and persistent provenance, so you always know which line of code produced the button in front of you. In three decades he never saw that handoff close, because design and engineering optimize for different outcomes. When a single intelligence could both read design intent and write code, he thought the loop might finally shut. It did not. He tried five tool setups for a bidirectional roundtrip and every one was lossy: bindings dropped, or a design change survived while the code did not. So he built ReWeaver, demonstrated publicly here for the first time, with generated code on one side, a Figma canvas on the other, and a button marked show drift. It scans both and reports across dimensions including design quality, performance, tokens, and accessibility, which he carries from his years at Microsoft. Models still emit components with no ARIA live region, so a screen reader announces nothing. Running twelve iterations on one codebase, pure model output started near thirty percent fidelity and decayed, while deterministic guardrails held it up. It never reaches a hundred, because the last stretch is human judgment. His name for drift that accumulates unwatched is the new tech debt. Speaker info: - https://x.com/reweaver_ai - https://www.linkedin.com/in/jongor/ - https://www.reweaver.ai Timestamps: 0:00 - Losing the speaker notes, and what a roundtrip means 2:10 - Thirty years of handoffs that never closed 3:37 - Going all in on vibe coding 5:27 - The innerHTML moment that made him read the code 6:20 - Testing the claim that the roundtrip is solved 7:40 - A harness with code on one side, design on the other 9:33 - Show drift, accessibility, and what it catches 11:50 - Deterministic guardrails versus pure model output 14:06 - Human in control, not just in the loop 16:25 - Nine dimensions, and trying it yourself

Join the discussion

Sign in to join the discussion

Sign in