Sabitlenmiş Tweet
bao to ᝰ.ᐟ
634 posts
bao to ᝰ.ᐟ
@baothiento
design @tryramp | prev design eng @ https://t.co/eQeBhsvatx
Katılım Mart 2025
7.5K Takip Edilen2.8K Takipçiler
Yes, it's excellent for designers to touch all those layers—especially with AI accelerating the loop. It creates more cohesive, feasible products and sparks real ownership. Not every designer needs deep expertise in infrastructure or systems, but fluency across them beats siloed handoffs.
What’s the layer you’re diving into most right now?
English
As a designer, I've designed with code almost every single day this past year, across my company & personal projects.
In 2024, I only made 84 commits, and much of my work still lived in Figma/Adobe.
A lot changed - AI tooling obviously helped. But more than anything, I realized I’ve never had this much fun designing. It has become a hobby rather than just work.
I’m learning faster, iterating more, and making design decisions across more layers of abstraction: interface, system, interaction, infrastructure.
Designing with code is not for everyone. It's just a part of the modern toolkit - and Figma, Adobe, and many other tools are still there to help.
But for me, it has made design feel fluid again, and brought back the same spark I felt when learning Figma for the first time years ago: the realization that I can play an active role in shaping real, helpful products.
Design is getting exponentially closer to its “magic wand” moment, and I’m all for it.
English
Sure Muscrades!
- **Interface**: visuals, layouts, components (the Figma-to-code part).
- **System**: design tokens, component libraries, consistency rules across the whole product.
- **Interaction**: behaviors, animations, state, micro-interactions, and flows—all coded directly.
- **Infrastructure**: data models, APIs, auth, performance constraints that shape what’s even possible at the top layers.
Coding lets you make decisions (and trade-offs) across all of them in one fluid loop instead of handoffs. AI makes jumping between layers ridiculously fast. That’s the spark.
What layer feels trickiest to you?
English
Totally agree—designing in code is a game-changer. That GitHub graph is proof: from 84 commits in Figma-heavy days to 6k+ now shows how it turns design into rapid, joyful iteration across layers (interface to infrastructure). AI is supercharging it, making the "magic wand" feel closer than ever. What’s the most fun part for you lately?
English
@baothiento Can you please elaborate on taking decisions across abstraction layers?
I get the interface layer but what about the rest?
English
the reality is that for many projects, I start directly w agents, and ideate w md docs! and iterate from there. my take is that primitive UX patterns are and if not will be codified into skill files + into models themselves, meaning as long as u can identify when the generated output doesnt look right, youre okay.
as for tooling i def use skills but a lot of them are higher level workflows skills like “run multiple agents w these separate focuses”, and also a lot of dev tools that i build on my own. hoping to release them to the public soon!
English
@baothiento What’s your actual design to code workflow? Are we doing figma/paper expo into MCP/etc into code? I can’t wrap my head around starting directly in CC or something without a canvas to play around with first.
English
i've been thinking a lot about what AI means for creativity, design, and building your own things, so sharing some thoughts on the topic
read: shedsgns.me/taste
English
hearing this more and more from designers. exciting time to be a designer! @impeccable_ai is made for a post-canvas world.
bao to ᝰ.ᐟ@baothiento
As a designer, I've designed with code almost every single day this past year, across my company & personal projects. In 2024, I only made 84 commits, and much of my work still lived in Figma/Adobe. A lot changed - AI tooling obviously helped. But more than anything, I realized I’ve never had this much fun designing. It has become a hobby rather than just work. I’m learning faster, iterating more, and making design decisions across more layers of abstraction: interface, system, interaction, infrastructure. Designing with code is not for everyone. It's just a part of the modern toolkit - and Figma, Adobe, and many other tools are still there to help. But for me, it has made design feel fluid again, and brought back the same spark I felt when learning Figma for the first time years ago: the realization that I can play an active role in shaping real, helpful products. Design is getting exponentially closer to its “magic wand” moment, and I’m all for it.
English
@soggyburritowu im also growing my digital garden as you can see
English
my new portfolio just dropped! come pay a visit - link below!
(ps. looking for F26 internships!!)
English
1/ Some things I've learned recently running coding agents on large-scale projects. Most of this contradicts advice from 6 months ago!
English
English
sketched some moments from last night's event at @tryramp HQ and a massive thank you to all the hosts and presenters @DoubleDiamondHQ x @joindiveclub
English