People teach UX as a department and testing as a gate. For a designer who was told to code, and for the one who still does not like code, both are studio skills with better lighting. They are how you keep observation and opinion when a prompt can spit a whole interface.
UX and UI are form. They are how a body meets a shape: a button that has a weight, a flow that has a rhythm, a page that either holds or spills. You already know this from rooms, from books, from a poster that can be read at three meters. Interface work is not a promotion out of art. It is art that has to survive a hand.
Testing is a creative seeing method. You put the form in front of someone who does not love you, and you watch where their eye and their mouse hesitate. That hesitation is information the way a smudge on a proof is information. You are not "validating a hypothesis for stakeholders." You are looking. Looking is how direction gets evidence.
This is the same scarce skill as judgment in code review and curatorial work: someone has to choose what holds. It is the same pressure as they told you to code, you need taste.
UI as pattern, not decoration
A good UI is a repeating structure that can take variation without collapsing. That is a grid. That is a type scale. That is a node graph with a stable output. When designers say "system," they mean a pattern you can run again, the same way a loop runs a motif.
If you are coming from canvas work, do not start with a 40-page design system. Start with one screen that has:
- One primary action with a real weight
- One quiet secondary action
- Type that can be read in bad light
- A state for empty, a state for error, a state for done
Those states are composition problems. Empty is negative space. Error is contrast. Done is resolution. You have been solving these with color and margin for years.
Wire that screen in the same appetite you would give a sketch: a small batch, a circuit breaker, no extra settings page "while you are in there."
Testing as looking, not as theater
A test that exists to produce a slide is theater. A test that exists so you can see is craft.
Three cheap seeing methods:
- Sit behind one person. Give them a task ("export the poster"). Do not speak for two minutes. Write where they pause. That pause is your composition talking.
- Change one variable. Like a p5.js sketch: only the label, or only the contrast, or only the order. If you change five things, you cannot see.
- Write the expected mark first. "When they click export, a file appears in ten seconds." That sentence is a test. Automation can wait. The seeing cannot.
Automated tests later are just a way to keep the pattern from drifting when you are tired. They are not a personality. They are a second pair of eyes that does not get bored. Use them when the form is stable enough to name.
If you skip the human sitting and jump to tooling, you will get a green pipeline and a dead product. The artist who becomes a coder keeps the sitting.
Morning Pages still belong here
Before a test session, three handwritten pages. Not a script for the user. Empty the wish that they will love it. Cameron's Censor shows up in research as "I will explain the interface so they get it." If you have to explain it, the form is not done.
After the session, an Artist Date: leave the building. Look at a signage system, a ticket machine, a menu that works when you are hungry. Bring one pattern back.
The Artist's Way in the Age of AI is the companion for this: discernment is the scarce product when generation is cheap. Testing is how discernment gets evidence without becoming a cult of metrics.
Opinion in the interface
A screen without an opinion is a costume. Fashionable spacing, no weight on the primary action, five ways to do the same job: that is too many options rendered as UI. Your job is to make the next click obvious and to kill the rest.
If you do not write the code, you still own that crop. Sit in the review. Point at the extra state. That is taste in code without a commit.
How the notes fit
- They asked for code. You need taste, observation, opinion, and direction.
- Start with a visible shape, not a syntax course.
- Give the work an appetite and a circuit breaker so it can finish.
- Use a node-based visual system when you need to see the flow as a drawing.
- Treat UX as form and testing as seeing, so the shape survives contact with a stranger.
- Practice what not to build.
None of this requires you to start liking code. It requires you to keep seeing. If a person can use the thing without a tour, and still feel that someone with taste was in the room, the work did its job. That is the same bar as any other form you would sign.