Someone in a hiring loop, a stand-up, or a well-meaning friend said it: you need to code.
If you are a designer or an artist, that sentence often lands as a verdict on your usefulness. You do not like terminals. You do not like compiler errors. You like form, proportion, and the moment a surface starts to hold. Being told to become a programmer can feel like being told to abandon the only sense that ever made your work true.
Here is the quieter fact: you were not missing syntax. You were being asked for direction under cheap production.
The industry says "learn to code" because generation got cheap. Drafts, screens, and automations appear faster than anyone can honestly stand behind them. In that climate, the scarce product is not another person who can type. It is a person who can look, have an opinion, and say what belongs. That is judgment as the scarce product. It is also taste that cannot hide when generation is infinite.
This series is for you if:
- you are starting to code and already resent the courses
- you do not like code and still keep getting told it is the ticket
- you can already see when a product is ugly in the soul, and you want language for refusing it
- you want observation, opinion, and direction, not a new identity as "technical"
You do not have to become a coder in the costume they sell. You have to develop taste in code: the ability to tell a living system from a pile of plausible files, and the spine to choose what not to build.
Four things they actually wanted
When people say "designers should code," they usually mean four cheaper words and never say them.
Observation. Can you sit with a running thing and see where it lies? Not the mock. The click, the load, the empty state, the moment a user flinches.
Opinion. Can you say this interaction is wrong even when it is fashionable? Can you say this stack is a costume? Opinion is not mood. It is a defended cut.
Direction. Can you point the next week of work? One surface, one rule, one refusal. Direction is what too many options exists to avoid.
Taste in code. Not elegant algorithms. Taste as in: this module is doing two jobs. This state is a lie. This feature is a shrine to the tool. This is worth six evenings. That is not.
Syntax can be hired, generated, or sat beside. Those four cannot.
Why "just learn to code" is a bad brief
It treats your dislike of code as a character flaw. Often it is a taste signal. You dislike code that has no form: files that do not compose, tools that hide the drawing, tickets that never become a shape you can see.
The Artist's Way in the Age of AI already named the injury: infinite generation attacks nerve and discernment before it attacks craft. Forcing a designer through a syntax-first bootcamp trains the Censor, not the eye. You will get faster at performing "technical" and slower at the observation that made you hireable.
If you start at all, start as shape, not syntax. Make a mark the machine can repeat. Then stop. Taste grows in the gap between marks, not in the stack you can name at a mixer.
What to build right
Build the smallest form that can be used and felt. That is the same thesis as complex ideas into clear forms. A loop that draws a field. A node graph that shows one flow. A screen with one primary action that has weight.
Build where your observation is already dense: type, space, sequence, the body in a room, the hand on a surface. Do not start by cloning a SaaS dashboard you do not believe in. That is how people who hate code learn to hate themselves.
Build on an appetite, not an estimate. Shape Up is useful here because it forces the question "what is this worth" before "how long will it take." If it is not worth two weeks of evenings, it is a mood. See appetite, not estimates.
What not to build
Do not build a second brain, a personal OS, a no-code empire, or a clone of last year's Y Combinator screenshot. Those are shelters. They look like ambition and they hide the fact that you have not chosen.
Do not build authentication, payments, or a design system of forty tokens as your first coded object. Those are other people's problems wearing a learning costume.
Do not build because a thread said designers who cannot ship are obsolete. Obsolescence, in this decade, is people who can ship anything and will not say no. Direction is a no that still points.
Do not build to prove you like code. If you do not like it, you are allowed to stay a designer who can read a graph, sit in a review, and kill a feature. That is already technical work. It is the technical work that survives vibe coding.
How this series is meant to be read
Read it as one argument in eight notes, not as a course:
- You need taste in code, not a new personality.
- Start with shape you can see.
- Give the work an appetite and a circuit breaker.
- Use node graphs when you need the drawing to stay visible.
- Treat UX and testing as seeing, not as departments.
- Practice refusal: what not to build when typing is cheap.
- Enjoy the run: generate a thousand, keep 3 percent, let the cull train taste.
- When 300 files still have dump names, try the tools like shoes. Classic for some. Running for others.
Morning Pages still belong at the front of the week. Three handwritten pages. Not a standup. An Artist Date once a week that is not a tutorial. That is how observation stays yours.
If you leave this page with one sentence, take this one: they asked you to code because they cannot staff direction. Keep the direction. Learn only as much code as your taste requires to stay honest.