Bridging Design and Engineering: The Coding Connection

Title: Designing in the Medium: Why Design Needs Engineers Who Code

It’s hard to even articulate this scenario with words and pictures. Sometimes you just have to feel it, use it, to understand the nuances.
This all might seem obvious — but the obvious is not always implemented. Sometimes it’s not as obvious as you might think. And sometimes the obvious is just too much work, so it gets skipped.
The point is: look and feel is hard to design, let alone spec, in a design tool. You need someone who understands what’s possible in the medium (and I mean the medium you’ll deliver the interaction in, not the medium you’ll design it in — those can be different).
You need someone who can do design work with code.[1]

The idea
Design and engineering are not sequential handoffs but intertwined practices best performed together in the final medium. Static mockups in tools like Figma capture intentions but lose the nuances that only emerge when interacting with real code in a browser or app. A “design engineer” bridges this gap—someone who designs with code, iterating directly in the delivery medium to discover what feels intentional, responsive, and alive. Without this, products risk feeling assembled rather than crafted, with details that only reveal themselves too late.

Who said it (and the context)
Jim Nielsen, a web designer and developer who writes at blog.jim-nielsen.com, makes this case in his ongoing series on design engineering. Drawing from years of building interfaces, Nielsen argues that the traditional split between designers (who produce specs) and engineers (who implement them) creates friction, slow learning, and diluted results. He advocates either a single person fluent in both or tight, ongoing collaboration so that “making” itself reveals new correspondences of meaning.[1]

A small expansion
The medium matters because it is where constraints, possibilities, and feedback loops actually live. Designing a responsive layout by resizing a browser window in real time teaches lessons that no static mockup can convey. Prototyping interactions in code uncovers micro-details—hover states, loading behaviors, edge cases—that only surface through use. This is not about forcing every designer to become a coder; it is about ensuring the final experience is shaped by someone who can feel and adjust it in its native form. The result is work that feels “designed all the way through.”

Another lens on the idea
A complementary view comes from Bret Victor’s emphasis on immediate creator-creation feedback (explored previously on the site). Where Nielsen focuses on the practical bridge between design and code, Victor highlights how tight loops between intention and outcome accelerate discovery. Both reject waterfall separation in favor of responsive making—whether through code, prototypes, or material engagement—aligning with the newsletter’s recurring thread of attentive, iterative craft.

Why this matters across art and design

  • Visual identity: Brand systems gain coherence when logos, animations, and responsive behaviors are refined in the actual delivery medium rather than translated later.
  • Product & UX: Interfaces feel more alive when micro-interactions and layout decisions are tested and adjusted in code from the start.
  • Architecture: Digital twins and interactive models benefit from the same principle—designers who can manipulate the real simulation environment.
  • Studio art: Generative or interactive works deepen when the artist works directly in the medium of execution.

Two quick drills

  1. Medium Sprint (30–60 minutes)
    Take a small design idea (a button, a card, a simple animation). Sketch it on paper, then immediately build a working version in code (HTML/CSS/JS or your preferred tool). Note what changed or emerged only in the medium.

  2. Handoff Reflection (ongoing)
    Review a recent project. Identify one element that was designed in one tool and implemented in another. Ask: What nuances were lost or gained in translation? Sketch or prototype one improvement made possible by working closer to the final medium.

Thread to remember
This edition extends the newsletter’s exploration of attentive making by emphasizing direct engagement with the delivery medium. It connects to prior discussions of iterative collaboration, unfolding processes, workmanship of risk, and the value of immediate feedback—reminding us that great design often requires getting our hands (or keyboards) on the thing itself.

Sources

  • Central idea drawn from Jim Nielsen’s “The Case For Design Engineers, Pt. II” on Barnsworth Burning.[1]
  • Supporting context from the same extract and related discussions on the site.
  • Complementary perspective informed by Bret Victor’s ideas (recurring across Barnsworth Burning extracts).

Try this today: Open a browser and recreate one small element from a current project directly in code. What does the medium teach you that your previous sketches did not?