Why I Started Caring About Design

I was a frontend developer who thought design was someone else's job. I built what was handed to me. I translated specs into code. If the Figma file looked off, that was the designer's problem. My job was to implement it correctly.

This lasted until I shipped something I was ashamed of.

What happened

A client had no designer. Small company, tight budget, no design resource. They had a rough wireframe in Figma — boxes and labels, nothing styled — and they wanted me to "make it look good."

I chose colors. I chose fonts. I chose spacing. I did this by looking at websites I liked and approximately copying their decisions without understanding them. I put in a serif heading because I'd seen that somewhere. I used a teal accent because it seemed "modern." I picked 14px body text because that's what I'd always used.

The site launched. The client was happy — they had nothing to compare it to.

But I knew. I knew the heading and body fonts didn't talk to each other. The spacing was inconsistent by 4px in ways I couldn't name but could feel. The teal didn't work with anything. The 14px body text was making people squint.

I'd built something technically correct and visually incoherent. And I couldn't explain why, which meant I couldn't fix it.

The real problem

I didn't have a vocabulary. I could see that something was wrong — I had eyes, I'd been using the internet for years, I had some accumulated sense of what looked right — but I couldn't name what was wrong or why.

Without the vocabulary, I couldn't improve deliberately. I could only guess.

So I started studying. Not the tactical stuff — not "use these font pairings" or "these are good color palettes." The underlying stuff: why does consistent type scale create rhythm? What does contrast actually do in a composition? Why does 8px spacing feel different from 10px?

What I found out

Design is not decoration. It's the management of attention.

Every element on a screen is competing for the user's attention, and good design decides which ones win and in what order. Hierarchy, contrast, whitespace, color — these are all tools for controlling that competition.

When my site looked wrong, it was because I'd created a scene where everything was competing equally. No hierarchy. No decision about what mattered. The user's eye had nowhere to go.

That was fixable — but only once I understood what I was fixing.

How this changed my work

I stopped treating design as a handoff. I started treating it as a shared problem between Figma and the browser.

When I receive a design now, I don't just translate — I interrogate. What is this trying to do? Does this spacing decision serve the reading pattern? Does this color work in the system or just in isolation?

Sometimes this means pushing back on a design. Sometimes it means catching in the browser something that looked fine in Figma but doesn't work in motion. Both require caring about design, not just implementing it.

The title "Design Engineer" is not a hybrid of two jobs. It's a single discipline where the seam between design and code disappears — because the person holding the tool can think in both directions at once.

I didn't plan to become that person. I became it because I shipped something I was ashamed of and decided not to do it again.