Part 2 -- Long Live The Designer.

In 300 — Zack Snyder's 2006 film ( I have see it willingly and unwillingly at least a half dozen times), the one that gave every gym in America a motivational poster and every design studio a moodboard it would spend the next decade trying to forget, there is a scene that has nothing to do with battle. The young Leonidas is sent into the wilderness alone. No instruction. No teacher. No structured feedback. The agoge doesn't teach him what to do out there. It puts him in conditions where he has to figure it out, or not come back.

He comes back having killed a wolf, using a narrow pass in the rock to neutralize the animal's advantage. He didn't learn that in a room. He learned it because the room wasn't available.

The Spartans understood something that most design education still doesn't: the difficulty is not incidental to the curriculum. It is the curriculum.

A different kind of curriculum

Most design education is protected by design. Critique happens in rooms where everyone cares. Work is evaluated on calibrated screens, in good light, by people who understand the intent. The conditions are managed. The feedback is structured. The stakes are low.

This is useful for learning language. It is not useful for developing judgment. Judgment forms under pressure, in conditions you didn’t control, against feedback that doesn’t care about your intent. It forms when something you believed in fails in the real world, and you have to understand why.

There is a model that takes this seriously. It is built around a simple principle: nothing earns the right to exist until it has been tested against reality. Not the reality of a presentation room — the reality of a bad print, a wrong surface, a distracted reader, a shelf it has to compete on, a hand that handles it without care. You build it. You subject it to conditions it wasn’t designed for. You see what holds and what doesn’t. If it survives, it moves forward. If it doesn’t, it gets thrown out.

But the trash is not a failure state. It is the most honest feedback a piece of work can receive. And learning to read why something ended up there — not just that it failed, but what specifically gave way and under what pressure — is the education. That’s the thing that builds the eye that AI cannot replicate and cannot provide.

This isn’t an argument for cruelty or for discarding people who don’t fit a narrow mold. It’s an argument for consequence. For building environments where the work is actually tested, where failure is informative rather than shameful, and where the feedback comes from reality rather than from a room full of people who are already convinced.

Taste is not what is beautiful

The word “taste” carries a lot of unfortunate baggage. It suggests refinement, preference, the ability to recognize quality in expensive things. That’s not what I mean.

Taste, in the context of design practice, is the ability to know what matters under constraint — what to keep, what to cut, what is doing work and what is decoration, what will hold up and what will fall apart. It is judgment under pressure. And it is built, not inherited.

The designers who develop genuine taste through rigorous real-world testing arrive at a definition that is more useful and more honest than the aesthetic one: taste is not what is beautiful. Taste is what survives.

A mark that reads on a napkin and on a billboard. A layout that communicates in three seconds to someone who isn’t trying. A system that holds together when a junior person applies it without supervision, in a context that wasn’t anticipated, at a scale that wasn’t specified. What survives those conditions is good. What doesn’t is not, regardless of how it looked in the presentation.

This is what AI cannot teach — not because the technology is limited, but because the lesson requires contact with the real world. You cannot learn what survives without exposing things to the conditions that test survival. You cannot develop the eye for it without watching things fail and understanding why.