Code Isn't as Scary as It Used to Be

Designers are learning to change application code directly with Claude Code, and the early results are faster and better. Here's what's changing, what it means for Figma, and how to start.

Hand-drawn illustration of a computer terminal window showing a command prompt

I've been circling one realization for a few weeks now: designers should be able to work in code.

I'm not saying that to provoke anyone. I'm working with our development and design teams to train all of our designers to use Claude Code, so they can touch the code directly. Early indications are strong. Designers are creating experiences inside the applications themselves, they're moving much faster, and the output is better. It's early, so I'll hold that last claim loosely. It's the direction we keep seeing.

What changed

In my experience, code has always stood between a designer's idea and the thing a user touches. A designer drew it, a developer built it, and the handoff sat in the middle and was never quite right. The fear on the design side was reasonable. Code is a different discipline, that requires years of technical expertise and a steep learning curve, one wrong change could break something real.

AI has lowered that learning curve. With Claude Code, a designer can describe what they want in plain language and work on the real application. The syntax and the unfamiliar tooling now sit behind a conversation. That's why code is nowhere near as scary as it used to be.

What it looks like for us

We're building on several fronts at once: new applications, and the modernization of existing ones with AI. Many of these are small, fast-moving projects. Designers work directly with developers they already know well, and they iterate quickly.

Some training is needed. Designers have to work closely with developers while they learn. That relationship is the part I'd stress most. It already works dramatically better and faster for us, and I think it works best where design and development already have a strong working relationship. If you don't have that yet, I'd build it first.

Nothing has gone particularly wrong so far, and the results are very impressive, and the output experiences are richer and more suited to customer requirements.

And Figma?

Honestly, we're not sure Figma fits our process anymore. It's still there as a repository of information. But designers are using it less and less. When a designer can work on the real application directly, I think a picture of that application becomes less necessary. The source of truth is always the code. Designs in Figma are always riddled with ideas, things that didn't make it through refinement etc.

What it means for designers in an enterprise

Let me be clear about what I'm not saying. Designers shouldn't think of themselves as engineers, and we shouldn't own the code. Owning the code of an application is a developer's expertise, and it belongs with the development teams.

What I am saying is that designers should be able to affect the code directly. That means fixing the small issues we spot ourselves, and using code to generate new experiences and showcase ideas, instead of only describing them in a file. A working idea is a far better starting point for a conversation.

The aim is to work more closely with our development teams and get to the experience we know customers will love. That's why the working relationship matters so much. Developers bring the architecture, the standards and the judgment that comes from knowing the codebase. Designers bring a clear view of the experience, and the closer the two get, the faster that view reaches customers.

What surprised me

I've always been curious about development, but I never had the time to go beyond some basic websites. What surprised me most was how readily the code came once I started working with Claude. It's reignited a passion I'd half forgotten. I'm getting more ambitious now, building local applications for myself to do certain tasks.

If you want to try it

Build something local first. Pick any idea. It really doesn't matter which one. Open the tools, ask Claude for help, and start making something. The first project isn't the point. Finding out that you can do this will change how you think about all of this.