I typed one prompt, something like "design me an onboarding screen for a booking app, teal palette, three steps." Hit enter. Counted in my head: one, two, three, four, five. The screen appeared. Clean layout, nice whitespace, sensible type, even left room for a "skip" button. I sat there looking at it, mouth slightly open.

Then a strange feeling crept in. Not quite joy. That screen — I'd once spent several nights learning how to make it. Learning grids, learning spacing, learning why the eye travels this way and not that way. And the machine did it in five seconds, before I'd even sipped my coffee.

The question surfaced very quietly, and it stung: so all the stuff I grind on every night — does it still mean anything?

That worry has a name

It took me a while to name the feeling. It's tech anxiety — the sense that the ground under your feet is shifting faster than you can find your footing.

And it doesn't just appear in my head. It gets fed every day by the stream of information I scroll past. Open the phone and there it is: "AI will replace designers in two years." "The field is dead, why even study it." "My cousin in eleventh grade is already building apps with AI." Each headline is a tiny dose of panic. They stack into a thick, toxic air — and the newcomers, people like us, breathe in the most of it.

Here's where the poison sits: it doesn't attack your skill. It attacks your will. It doesn't say "you did this wrong." It says "why bother trying." A criticism leaves you something to fix. A line that makes you let go takes away even the chance to get good.

I've watched a lot of people quit right at this stretch. Not because they were weak. Because they got tired of having to convince themselves, every single day, that what they were doing still counted.

The machine is fast — but fast at what?

Sitting with that AI-drawn screen long enough, I started to notice something.

It was pretty. But it didn't know why. It didn't know my users were night-shift nurses with busy hands and tired eyes who just want to tap quickly. It didn't know that clinic is busiest at seven in the morning. It didn't ask "wait, why is this step even necessary?" It gave me a very smooth answer to a question that I'm the one who has to ask.

That's when I understood where the machine is fast, and where it's slow.

Technology can produce an answer in five seconds. But knowing the right question to ask still takes a human who has lived, failed, and felt.

Problem-solving isn't something you download overnight. Neither is empathy — the ability to sit down and imagine you're that frustrated user. Those things build slowly, layer by layer, through every project you break and rebuild.

So I changed my approach. I stopped reading the "AI is coming for your job" pieces — they gave me no new skill, only drained my energy. I started treating AI like a brilliant, lightning-fast intern: it does the draft, I do the judgment. It frames a screen in five seconds, I sit and fix that frame to fit real people. The "fixing it right" part is the actual craft. And that's exactly what I'm quietly getting better at every night.

I'm not going to tell you not to worry. Worrying is fine. I worry too. Anything new tilts you a little, and being tilted is nothing to be ashamed of.

I just want to remind you of one small thing: the machine is running a sprint, and your career is a long-distance run. The person who finishes isn't the one who accelerated hardest in the first kilometer — it's the one with legs left at the thirtieth.

So tonight, open the laptop. Learn a little more. Fix one more frame. Let the machine be fast. You just stay calm and keep walking.