Can we talk about how a CSS typo turned my design system review into a joke session?

I was showing our design system to the bosses last week. I had a typo in my code that made all buttons say 'subnit'. Everyone started laughing really hard. It was funny but also pretty embarrassing. Now I check my work twice before any big meeting.

3 comments

3 Comments

coleman.derek1mo ago

Typos in code reviews are the worst, especially when everyone sees them. I once had a similar thing happen with a misspelled variable name that made our app display nonsense. It was during a demo for a client, and the whole screen kept showing 'error' messages because of it. My boss had to step in and explain while I was frantically trying to fix it live. Now I always run a spell check on my code comments and strings before any presentation. I mean, it's crazy how one little mistake can throw off everything.

lily_sullivan821mo ago

Seriously, that demo story is a nightmare. I always figured typos were just cosmetic, but seeing how they can break a live presentation is eye-opening. How do you even recover from something like that in front of a client? It makes me realize that every detail counts, especially when stakes are high. I guess I'll be running spell checks on my code too now. Who knew spelling could be so critical in coding?

river_wright25d ago

Honestly those demo stories sound rough but maybe we're overthinking it. @lily_sullivan82 I get the fear, but sometimes a typo can actually break the ice. That 'subnit' button probably made the bosses remember the system more. My team once had a login error message say "you done goofed" because of a typo. The client laughed and said it was refreshing. It showed we were human and they relaxed for the rest of the meeting. Not every typo is a disaster, sometimes it's just a funny moment.