There's a weird thing that happens in most product teams. Designers hand off their work to engineers, and somewhere in that translation something gets lost — the intention, the nuance, the feel of the thing.
The handoff problem
It's not anyone's fault. Design tools and code speak fundamentally different languages. A designer thinks in constraints and relationships. An engineer thinks in logic and systems. The file in between — whether it's a shared link or a screenshot with redlines — doesn't actually bridge that gap.
What it does is defer the gap. The hard conversations about "what does this do on mobile?" and "what happens when this text is three times longer?" get pushed to implementation, where they're expensive to revisit.
What I've learned building both sides
When you design and build, the gap closes in both directions. You design more conservatively because you know what's hard to implement well. You build more carefully because you feel the design intent from the inside.
The result isn't less ambitious design — it's design that actually ships the way it was imagined.
The best interface is the one that works exactly as its designer intended.
This is why I think "design engineering" is less a job title and more a way of working. It's not about knowing every CSS property. It's about never losing the thread between intention and output.
On tools
Good tools get out of the way. The best ones make you forget you're using them at all — which is precisely the feeling you're trying to create for the people using what you build.
There's a kind of recursive satisfaction in that.