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
- Inside Design at Shopify: How to Grow as a Designer When Everything Is Changingyoutube.com
- Annotating for agentsbenji.org
- Agentic Computingjzhao.xyz
- Code was our medium for thoughtwattenberger.com
- Building Effective AI Agents \ Anthropicanthropic.com
- Scaling long-running autonomous coding · Cursorcursor.com
- Thoughts on slowing the fuck downmariozechner.at
- How Design Tools Like Figma and Canva Are Impacting Designers | Futurefuture.a16z.com
- One Developer, Two Dozen Agents, Zero Alignmentmaggieappleton.com
- Thoughts and Feelings around Claude Design · Sam Henri Goldsamhenri.gold
- Why We Built Our Own Background Agentbuilders.ramp.com
- Don’t Build Multi-Agents | Cognitioncognition.ai