Where the spectrum lives
Design engineering sits between two instincts: the designer's need to make the interaction feel right, and the engineer's need to make the system behave correctly. The middle is where prototypes, design systems, motion, handoff, and production constraints start shaping one another.
Why the gap is a superpower
When I can move between Figma, HTML, and product code, I can test the part static screens hide: timing, state changes, empty states, resizing, and the feel of an action. That makes feedback sharper because the review is about the real interaction, not a guessed version of it.
How I show up on the spectrum
I use code when the experience depends on behavior, and design tools when the problem is visual judgment. For public work, that shows up in DeFi Triangle, password-UX prototypes, and portfolio interactions. For employer work, the detailed examples stay protected by NDA, but the same practice applies: make the behavior tangible before asking people to approve it.