Introduction
"Bridging the gap between design and development."
If you've worked in this industry for any length of time, you've sat through that conversation more times than you can count. On panels, in retros, in every job description that ever asked for a "designer who can code."
For ten or fifteen years, it stayed a conversation.
Today, it's starting to become real.
I wrote recently about design moving into production — coded prototypes, the real design system, Figma becoming documentation. This is the next question underneath that: if the two silos really are coming together, what happens to the roles?
Why it's different this time
What's changed is that designers can now communicate in code, not just in rectangles.
The thing we describe in words, or draw with frames in Figma, can now be executed as working, coded prototypes. When a designer can speak the same language as the developer they hand off to — or skip the handoff entirely — the gap stops behaving like a gap. The two separate silos start coming together to deliver one experience.
A framework for the blur
Boris Cherny, who created Claude Code at Anthropic, recently put words to this. Looking at his own team, he described engineering, product, design and data science starting to "melt into a new kind of role", and grouped the people he works with into five archetypes:
- Prototyper — generates ideas fast, most of which never ship.
- Builder — turns a prototype into something production-ready.
- Sweeper — simplifies, cleans up, and makes things faster.
- Grower — takes something that exists and iterates it toward better product-market fit.
- Maintainer — keeps a mature product reliable and secure as it scales.
His key point is the interesting one: these archetypes aren't tied to job titles anymore. A designer, an engineer, or a PM can fill any of them, and a healthy team carries a mix of all five.
Melt, or blend?
I love this framing. But I'd push on one word.
Melt sounds seamless — like the roles dissolve into a single thing. I don't think that's quite right. I think what we'll actually get is a blend, not a melt.
A blend combines the ingredients without erasing them. There's still core craft in there. A great prototyper and a great maintainer are not the same person, and I don't think they should be. The disciplines don't disappear — they just start working far closer together than the old silos ever allowed.
And how good that blend turns out? That depends entirely on your blender.
Or, put another way, your workplace. ;)
Which one am I?
Of Boris's five, I see myself as a Prototyper, a Builder, and a Grower.
The first two are where I start — getting an idea into something real. But Grower is where I think the real value sits: taking something that's been prototyped and built, and iterating on it until it genuinely fits.
A recent example is Sage Studio, an internal tool for designers to share work, leave async feedback, and gather inspiration together. The concept was my Team Lead Kyle Mayne's, but I contributed to the whole design and a significant part of the build.
On that one project, I moved between prototyping, building, and growing — without once changing job title. (I'll write more about Sage Studio soon.)
Where this leaves the gap
This is the part I find most exciting as a designer.
For years, the gap between design and development was something we talked about closing. The difference now is that it's actually closing — not because someone finally bridged it, but because the two sides have a shared language for the first time.
The thing we used to design with rectangles and hand over is now something we can describe, build, and grow ourselves — alongside the developers we once threw it over the fence to.
The conversation is finally becoming a reality.
We just need to get good with the blender.