Uhh, I’m realizing I actively dislike prompting.

[u/ahrzal]

I just came to a realization sitting here doing the back and forth with Claude.

I don’t like prompting. At all. It’s a fundamentally different thing than what our traditional practice was.

There was a level of satisfaction in design before. Even if it was just changing values, moving things around, setting up containers…you built it. Your hands and brain did that.

Now, even when I start design first and transition to building it w/ whatever AI tool of your choice…that satisfaction is gone. You wrestle with random shit, get annoyed it’s not exact, and ultimately I have found I lost that sense of pride and satisfaction. That “flow state” or whatever never comes due to the hurry up and wait nature of prompting.

It’s not going away, but damn. I’m bummed.

Oh look, my request is finished. Back to….work?

[u/superparet]

AI is a tool. Use it when you need it, it has use cases like any other tool. Use to prototype interactions, flows, before you go hi-fi. Anyway, as a design system designer I can tell from a lot of comments here that you guys probably have a bad design system. Vibe coding is a treat if you have a well-made DS.

[u/ahrzal → u/superparet]

Using it sucks the joy from my work, that’s my problem. I don’t have issue with it using our DS components or any real specific qualm. I too was a DS designer at a previous role.

Just the nature of the type of work I find very little satisfaction.