A few weeks ago I watched a video from a designer who’s built a decent chunk of her following on AI-assisted design content — and is the kind of creator who makes tutorials about wiring tools like Claude Code into Figma to spit out working prototypes, and other topics of that nature. To her credit, what she offers on her content platform is genuinely useful stuff, and is the kind of content I’d normally send to another designer without a second thought. But this time, before getting into any of that, she spent the first few minutes of the video walking through a detailed, thoughtful, well-articulated explanation of why designers shouldn’t code.
I sat there thinking, “Pretty please with a cherry on top: I beg you to stop talking.”
It’s not that she’s lacking nuance — there clearly is nuance. It’s not that she’s untalented — she obviously has talent. It’s that the entire premise of her opening is a waste of everyone’s time — hers included — and it’s a waste of time that’s become a genuine fixture in design discourse. Open LinkedIn, Reddit, or any design-adjacent corner of YouTube, and you will, with depressing regularity, find some designer popping into a feed or a comment section to explain at length what a designer’s job should and shouldn’t entail. Some of it is thoughtful. Most of it is wasted air. All of it is operating on a premise that’s fundamentally broken: that a designer’s opinion on the shape of their own job has any bearing on what that job actually becomes.
It doesn’t, because designers don’t decide what their responsibilities are. The market does.
I’m not saying that’s how it should be — and the goal of this post isn’t to relitigate capitalism. I’m just saying that’s how it is, and once you actually sit with why, the entire “should designers code” debate stops being a debate and starts being a distraction.
Scope Creep, Scope Decay, and the Thing Nobody’s Named Yet
Designers already have language for two ways a role can shift underneath you. Scope creep is when a project’s requirements quietly balloon past the original brief while you’re mid-engagement — you signed up for X, and now you’re also doing Y and Z, unpaid, because nobody drew a hard line. Scope decay is the inverse: the deliverables you were hired for gradually shrink, and you end up doing less, which usually means getting paid less. Both are considered bad for the same reason: in both cases, the designer loses money, either through free labor or through disappearing scope.
The third pattern is one that doesn’t have a name yet, so I’m giving it one: scope compression. Scope compression is when the standard expectations of more than one job get consolidated into a single title — not gradually or in the midst of a contract the way scope creep happens, but from the moment you’re hired. You don’t sign up as a UX designer and slowly get roped into UI work over eighteen months. You apply to become a “UI/UX Designer” because that’s simply what the job is now.
You’ve watched this happen, whether you immediately noticed it or not. Twenty-five years ago, UI and UX were entirely separate specializations, with separate people doing them. Fifteen years ago, those responsibilities started merging into a single discipline. Five years ago, that merge became the industry standard, and started absorbing writing expectations along with it. Today, the same field is compressing again, this time toward designers shipping actual code.
Design isn’t even the extreme case. Marketing is worse. Fifty years ago, marketing and design weren’t just separate jobs — they were separate departments, reporting up through entirely different chains of command. Today a marketer is routinely expected to manage ad spend, define demographics, write copy, design print collateral, run the website, and, in an increasing number of cases, shoot and edit video. Four or five jobs: one title, one paycheck.
It’s Not (Just) Capitalism
I can already hear the response to all of this, because it’s the same response attached to every narrative about shifting standards in the workplace: “hurr durr, the problem is capitalism.” And look — I get the impulse, and it’s not entirely wrong. But as a complete explanation it’s lazy, and it’s lazy in three specific ways:
- It assumes scope compression is always the direct product of corporate greed, when plenty of it isn’t, even if greedy companies benefit from it downstream.
- It implies that every convenience capitalism produces is inherently bad, which is a much bigger claim than anyone actually wants to defend.
- Finally, it suggests that reforming or eliminating capitalism would meaningfully slow scope compression down, and I don’t think this insinuation survives contact with how scope compression actually happens.
Here’s how scope compression actually happens, and none of it requires anyone to be evil.
The first driver is individual competitive escalation, and designers do this to themselves with no corporate villain required. Picture a UX designer job-hunting in 2005. She’s not just competing against other designers specialized in UX alone — she’s competing against a newer breed of professional who does UX and UI, because that combination makes them faster to hire. If enough people do this, the combined skillset stops being a differentiator and transitions to becoming the baseline. And once it’s the baseline, acquiring it isn’t optional anymore: it’s table stakes just to get looked at, regardless of whether the underlying work actually requires it.
The second driver is that innovation keeps lowering the cost of doing more. This isn’t some conspiracy — most of it comes from genuinely solving real friction. But the flip side of “the tool made X easier” is always “now the person using that tool can be expected to do more of A,B,C, X, Y, Z” and organizations adjust their expectations accordingly, almost by reflex. Even a designer who never once tried to out-hustle a competitor for a job still ends up pulled toward “know more, do more, be more,” purely because the tooling around them got more capable.
Put those two things together and you get the third point, which is the one that actually matters: even in some hypothetical world without capitalism, neither of those pressures disappear. People still compete for scarce roles. Tools still get better. Which means scope compression isn’t a glitch in the system, and it’s not even really a “feature” in the cynical, deliberate-design sense people mean when they say that. It’s an inevitability. It would show up under almost any economic system you can name, because it’s downstream of competition and tool-making, not downstream of any particular flavor of economics.
The Market Doesn’t Need You to Educate It
Here’s the part that actually explains why arguing with a job posting is pointless, and it’s more precise than “the market decides,” so stay with me.
Company hiring criteria is hardly invented out of thin air. Many times, the criteria is informed by precedent. When a company posts a listing looking for a marketer who can also build websites and shoot video, it’s very often because they already had somebody who did exactly that, and now that’s the bar.
And when the ask genuinely is fantasy — when a company wants something nobody realistically has — the market doesn’t need a designer to walk in and explain why that’s unreasonable. It corrects itself, automatically, through one of three outcomes. Either the company can’t find anyone and the role sits open indefinitely, or they find someone but have to pay well above what they budgeted, or — by far the most common outcome — they quietly lower the bar until the role becomes fillable at a price they’re willing to pay. Every one of those outcomes happens without a single designer successfully “educating” anybody about anything.
Which means any hiring expectation that actually sticks around long enough to become “the standard” is, by definition, something somebody out there is already meeting. The ridiculous asks that never get filled disappear on their own. The ones that survive aren’t ridiculous anymore — they’re just the new floor. So when a designer spends ten minutes of a YouTube video explaining why she thinks designers shouldn’t ship code, the honest answer is: it doesn’t fucking matter what they think, because they’re not the ones hiring every designer in the industry, and the market is already sorting this out without their input.
What Obsolescence Actually Looks Like
I’ve seen the endpoint of this up close, and it’s worth being honest about what it actually looks like, because it’s not dramatic. It’s quiet.
I once worked alongside a UX designer at an agency — good people, not naming names, not the point — who had genuinely excellent instincts. She was strong on usability, she was strong on accessibility, and was the kind of person who could look at a flow and immediately spot the friction everyone else missed. But she had no production knowledge whatsoever. No Figma. No tooling. No code. None of the mechanical, hands-on skillset that turns “this flow has a problem” into a fixed deliverable somebody can ship.
I want to be precise here, because it’d be easy to make this sound like a story about someone who didn’t deserve their job. She did. Her instincts were real and valuable. But being that specialized in a discipline that has compressed as much as design has didn’t just make her niche: it made her archaic. And the reason why is very simple: nearly every UI/UX designer getting hired in the modern job marketplace knows Figma at an absolute minimum — a soft-skills-only UX designer with zero production ability has gone from “specialist” to “rare enough to be almost anomalous” in the span of a few years.
That’s the model for what happens to designers who sit out the current shift. In about a decade, a designer who only does UX thinking paired with traditional User Interface Design — sans fluency with AI-assisted development tools — is going to look exactly how this designer looks today: a relic in their own industry, good instincts and all, standing next to a job posting that assumes a skillset they never picked up.
For what it’s worth, I’m not theorizing this from the sidelines. I’m a designer actively teaching myself to code specifically so I can ship it. And the designers I see actually landing jobs right now aren’t doing light UX thinking with a little UI production sprinkled on top. They’re doing UX, UI, and shipping usable code with ai-assisted platforms, full stop. To be clear, I don’t think shipping code becomes the absolute floor for every design job tomorrow. But I’m willing to bet that we have five years before it’s the expected norm — the point where a designer who only knows UX thinking and Figma, without any fluency in tools like Claude Code or Cursor, is functionally uncompetitive.
Learn the Skill or Don’t. Just Stop Talking About It.
None of this is a moral judgment on the woman in that YouTube video, or on the designer I used to work alongside, or on anyone currently making the “designers shouldn’t code” argument in a comment section somewhere on the internet. These aren’t fringe opinions from people with no stake in the industry — they’re actively held by people doing real work and teaching other people how to do it, which is exactly why the pattern is worth naming instead of dismissing.
But naming it doesn’t make it less true: pontificating about what a designer’s job should or shouldn’t include doesn’t make you more hireable, more relevant, or more competitive, no matter how well-reasoned the argument is. If you walked into a tech-facing profession assuming the skills that got you in the door would be the same skills keeping you employed a decade later, that assumption was always going to get proven wrong. Designers, engineers, and everyone else working alongside cutting-edge tools have never gotten the luxury of finishing their education: You’re a student for the entire run of your career, or you’re not doing this kind of work for very long.
Right now, the thing everyone’s being asked to learn is AI-native workflows — generating images, video, vectors, and yes, code — and no amount of explaining yourself to a client, a hiring manager, or a middle manager is going to change that fact. Scope compression doesn’t negotiate. It doesn’t care how eloquently you can explain why it shouldn’t apply to you. It’s not a debate you’re going to win by having better arguments than the market. Learn the skill, or don’t, and let the market sort out what happens next — because it’s going to sort it out either way.