Bugs. No one likes them, but they happen. Sometimes it’s a bug, a missed requirement, or something just isn’t done quite right. It’s happened to all of us at some point on a project, and more often than not it leads to frustration, anger, and an overall unpleasant experience.
Over time, though, I’ve found it’s better to accept these moments rather than fight them. A div is in the wrong place, a font is too bold, or a link points to a broken page. These things are inevitable. Why? Because we’re human.
We’re not perfect, and our work will never be perfect. The real issue isn’t the mistake; it’s how we respond to it. Was it an oversight? A rushed timeline? A genuine misunderstanding? Or someone avoiding responsibility altogether?
That’s the thing: bugs are inevitable. The problem is how we approach them.
If a timeline is tight and a request comes in at the last minute, you should expect something to slip through the cracks. That’s just reality. On the other hand, if something has been in progress for a while and doesn’t work as expected, and you are given a list of last-minute excuses, that frustration is understandable.
For me, if you find a bug in my work, 99% of the time I’ll acknowledge it quickly and propose a fix. If the issue exists because a feature wasn’t fully thought through, I’ll explain what happened and outline next steps.
What I won’t do is respond rudely. And I won’t let something ship without warning you it may not work as expected.
Because in the end, it’s not about the bug.
It’s about how we handle it. Check out this week’s blog post for the full write-up.