The people who code most with AI feel more valuable. Most of the profession is on the other side. This article is about them.

I ordered the roles by the vibe coding rate from the first article. The sentiment order is nearly identical. Design Engineers: 50% feel more valuable, 10.6% less secure. Researchers: 17.4% more valuable, 39.1% less secure (n=23, directional reading).

I did simple arithmetic: percentage saying “more valuable” minus percentage saying “less secure.”

• Design Engineer: +39.4 points
• Lead / Principal: +23.2
• Manager / Director: +11.8
• Non-designer: +7.0
• IC Designer: −7.6
• Researcher: −21.7 (directional)

Among designers, the IC is the only one with a negative net. And the IC is 58.3% of the sample.

Satisfaction with your own workflow, 1 to 10. People who generate nothing with AI give it 5.93. People who generate nearly everything give it 7.39. A difference of 1.46 points, and every intermediate step goes up.

Reading 1: adopting reduces fear. People who try it discover that AI expands what they can do alone, and start feeling more valuable. The fear is fear of the unknown.

Reading 2: fear blocks adoption. People who feel threatened avoid the tool that represents the threat, and fall further behind. The fear is rational and self-confirming.

I lean toward the second, because it explains the seniority paradox from the first article. Lead and Principal have autonomy and job security; they can experiment without the experiment looking like a confession. The IC, measured on delivery, can't.

The useful question isn't “why doesn't the IC adopt.” It's “what in the structure of the IC's work prevents it”. Deadlines measured in screens delivered. No protected time to experiment. Tools that need security approval. No technical peer to ask without embarrassment.

None of those items is solved by an AI course. All of them are solved by decisions made by whoever organizes the work. And the cost of not solving them is having most of your team feeling like they're on the losing side of a transition that, by the numbers, the people who cross it rate as positive.

Does fear block adoption, or does adoption reduce fear? And what changes in your answer if you're an IC?

What to do on Monday: if you lead, set aside protected, explicit time for ICs to experiment, with a real task and no delivery expectation. Pair a Design Engineer with an IC for one sprint. If you're an IC, pick a small prototype and generate the whole thing with AI this week, just to see what happens to your own net.

Asked to pick three investment priorities, designers put AI-generated code first, agents second and design systems with tokens third, ahead of canvas tools themselves. The fourth article is about why the design system became AI infrastructure.