✨ Be kind to yourself.

You’re not falling behind.
You’re not missing out.

You’re just learning how to work in a new world. 🌝

✨ Using AI well doesn’t mean using it more. Use it when it helps. Stop when it doesn’t.

Learn the tools. Become more fluent.

Build your toolbox.
Choose the right tool for the right workflow.

AI isn’t “magic”~

*poof*

✨ Speed removes natural stopping points. We have to create our own boundaries before the day fills itself.

I need a make a physical hard break or else I will never take breaks.

There will always be “one more prompt” … another “idea” … or another “refactor” 🥲

Hard boundary: no working on phone

✨ We’re not here to review infinite outputs. Pause. Pick a direction. Not every option needs our attention.

We also need to treat everything as a *draft* and remember the output is not perfect.

Maybe 70-80%. We need to refine it further and make the solution better.

✨ Our work is shifting from doing → deciding.

Then add *judging* for those of us creating AI infrastructure.

Decision fatigue (mixed with endless context switching) is real — make space to think, not just react.

Avoid getting to the point of decision paralysis or prompt spiraling. 😵‍💫

✨ When everything speeds up, expectations rise. We don’t have to match that pace everywhere.

Choose where it matters.

Gentle reminders to ourselves ✨

✨ Just because AI makes things faster doesn’t mean we *need* to do more. Notice the pressure to fill the gap.

AI fatigue is real and nobody talks about it · Siddhant Khare You're using AI to be more productive. So why are you more exhausted than ever? The paradox every engineer needs to confront.

Why I feel so tired 😪

“Creating is energizing.
Reviewing is draining.

There's research on this - the psychological difference between generative tasks and evaluative tasks.

Generative work gives you flow states.
Evaluative work gives you decision fatigue.”

siddhantkhare.com/writing/ai-f...

Structure. Rules. Skills.

Structured context. MCP servers.

Connecting the brain to the arms.

Automating. Scaling.

That’s what I’m coding lately.✨

The design system as AI Infrastructure.
Every single day.

Feel like we’re finally building a living + breathing design system. ✨

It’s like we’re really elevating the cultural and operational infrastructure of a design system.

Using new paradigms to elevate those very difficult parts of scaling a system.

Governance.
Contribution.

Making it a better maker experience to contribute and evolve the system. ✨

Coding the infrastructure.

Automating the boundaries + governance of a conceptual model.

Codifying the underlying invisible parts.

The parts that I always asked myself:
✨ How do I multiply my thinking to others?
✨ How do I help them see what I see?

The familiar flow state feeling of coding.

Being in the zone. Feeling productive.

Bringing ideas to life again. 🌝✨

But this time is not just coding components, tokens, styles.

It’s codifying all the things I learned over the years.

For months, we were deep in Figma, rebuilding.

In November, we started using Cursor.

It’s hard to explain how I have been feeling,

The feeling of returning back into the familiar space of coding in an IDE.

Surprisingly, not feeling as behind as I had feared before.

‪A year ago, I joined Snowflake. A design role again.‬

‪Throughout the 9 months of rebuilding of our design system, I did contribute though code in the same ways I did at Atlassian.‬

‪Defining ops. ‬
‪Writing a lot of documentation.‬
‪Restructuring foundations.‬

‪The context.

When I joined Atlassian 7 years ago, I left my role as a design engineer.

I stopped coding in that role.

I had an entire fleet of amazing devs that could code better.

I embraced building new skills in system thinking + design strategy + leadership.

In the back of my mind, I always missed coding.

As I increase my AI literacy and speed up my personal workflows, I find myself both very satisfied but also aware that I need to protect my boundaries even more to prevent myself from overworking. Need to pace myself. 🥲

How did bufo find us @dbanks.design @hipstersmoothie.com 😂 so random

Today was a *high five* day for us! @hipstersmoothie.com + @dbanks.design

Team work makes the dream work!✨

Reshaped is now open-source - Reshaped After five years of closed-source, Reshaped is finally open for all – both in React and Figma.

When starting Reshaped, having a paid license kept me going but also felt wrong sometimes. I wanted to give back more to the community. After 5 years – it is finally happening. Reshaped React and Figma libraries are now open-source.

reshaped.so/blog/reshape...

Get the links below ✨

One of my favs!

Design system fam reunited at Figma Schema 2025

South Bay design systems fam reunited @ Figma Schema ✨✨✨

@ventrebleu.bsky.social @dbanks.design @kaelig.fr @jenyee.social

Thanks for the lovely day @figma.com!

Not yet! We shall see in the future, still have a lot of Marie Kondo to do

It’s been a challenging 10 months. Crafted a vision, grew a dream team, and we’re co-creating an ai-ready design system.

We introduced the next generation of our design system to the company last week + beginning to launch all the things this week. ❇️

I love this feeling. 🌚✨

Finally figured out my password 🤣

Meeee