The Case for Canvas — Charlsy Yang
charlsyang.com · 970 words · saved by 1 readers
Design, writing, and thinking.
Designing with agentic coding tools is in and Figma is out—at least that’s the sentiment. After spending some time with these new tools, I do feel like they have a very different rhythm of making things. One common pattern of designing with agentic coding tools is parallelization: having multiple agents running at the same time working on different aspects of the UI. The benefit of parallelization is that I don’t have to wait for each agent to finish running, which is often the bottleneck (latency) and what breaks flow. The downside is it’s cognitively demanding to manage multiple threads of c
saved by
related reading
- AI Design Field Guideaidesignfieldguide.com
- Code was our medium for thoughtwattenberger.com
- Using AI as a Design Engineerjakub.kr
- AI Design Field Guideaidesignfieldguide.com
- Karri Saarinen on X: "Whenever a new design to code tool comes around, people get excited. It’s considered the holy grail of design. You can now design with code. This is the final evolution. But I don’t agree. It’s only the holy grail if yx.com
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- Tools for thought: science, design, art, craftsmanship? | Andy Matuschakandymatuschak.org
- Annotating for agentsbenji.org
- Vibe-coding limits a creator’s potentialconnieliu.work
- Jenny Wenjennywen.ca
- Harness design for long-running application developmentanthropic.com
- Output isn’t design - Linearlinear.app