Written on April 5, 2026

What the fuck is a designer after Codex?

If AI can generate decent UI and front-end code on demand, the designer's job shifts from making screens to making decisions.

For years, we treated design like it was mostly the act of making screens. Move the pixels. Pick the type. Make the flow. Ship the file. That was always incomplete, but now the gap is impossible to ignore. If Codex can produce interfaces, write front-end code, and generate ten decent options before lunch, then “the person who makes the screens” is no longer a very durable definition.

So what is a designer now?

A designer is the person who decides what matters. What should be there, and what should not. What needs to be clear. What needs to be quiet. What earns trust. What creates tension. What helps someone move forward without feeling confused, rushed, or small. When making goes faster, deciding becomes more valuable.

That means the work moves up a level. Less arranging, more noticing. Less polishing every corner by hand, more understanding what the product is trying to say. The designer becomes an editor, a translator, a curator of intent. Not just someone who makes the interface look good, but someone who helps it mean something.

Codex does not remove the need for design. It reveals what the job was actually about all along. The easy part to automate is the artifact. The hard part is the choice. After codex, a designer is the person still responsible for the decision, and for how that decision feels when it reaches another human being.