It works. Why can’t I leave it alone?

2 min read

You’re about to close the laptop.

Then you notice it. The heading feels slightly too far from the paragraph.

You move it up. Now the button underneath looks awkward. You adjust that too. Somewhere along the way, you decide the animation needs another look.

You were finished forty minutes ago.

I think frontend work attracts this kind of attention. You’re building something people can see, touch, and react to. Even when the code works, there’s still the question of how it feels.

A menu can open correctly and feel clumsy. Text can be readable and still tiring to get through. A button can look good until someone tries to use it on a smaller screen.

Caring about those things makes the work better. Sometimes a tiny adjustment really is worth the time.

The difficult part is knowing when you’ve crossed into fixing things because you can’t bear to call them finished.

You change a value, stare at it, then change it back. You’ve looked at the page for so long that you’re no longer sure which version feels right.

I understand why people connect good frontend work with perfectionism. The details are visible. Once you notice something, it can be difficult to ignore.

But I wonder whether getting better also means learning when to stop.

Someone using the page might still be struggling to find what they need while I’m deciding whether a shadow is slightly too dark. That thought brings things back into perspective.

I want to keep the part of me that notices. I also want to get better at deciding what deserves another hour.

Maybe closing the laptop is part of the work too. Leave it overnight. Come back. See whether the thing bothering you still matters.

How do you know when you’re making something better, and when you’re just finding it difficult to let go?

A thought in return

How do you know when you’re making something better, and when you’re just finding it difficult to let go?

Sent privately to Sandith.0 / 500 words