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 you value output higher than the process of design. Whenever" / X

x.com · 383 words · saved by 2 readers

To view keyboard shortcuts, press question mark View keyboard shortcuts Home Explore 20+ Notifications Chat Grok Lists Bookmarks Communities Premium Profile More Post Bhushan @b00shn Post See new posts Conversation Karri Saarinen @karrisaarinen 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 you value output higher than the process of design. Whenever a designer becomes more of a builder, some idealism and creativity dies. Not because building is bad, but because you start out including constraints earlier in the process than they should. I’m one that very much thinks design is ultimately what is shipped. But before it shipped, there is a lot of stages that don’t benefit from code or some implementation constraints. In architecture, a lot of the best work is started with sketches and some of the best architects st

Karri Saarinen @karrisaarinen 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 you value output higher than the process of design. Whenever a designer becomes more of a builder, some idealism and creativity dies. Not because building is bad, but because you start out including constraints earlier in the process than they should. I’m one that very much thinks design is ultimately what is shipped. But before it shipped, there is a

saved by

related reading