Stop apologizing for bugs

The point of a code review or any review for that matter is to identify whether the work is up to the standard it needs to be and where improvements can be made, if necessary. You're taking what is a review of your work as a personal attack and getting defensive. I think this is a very narrow-minded way of looking at things.

I completely agree. As humans, we're imperfect, and thus we're going to naturally make mistake. One person can't think of every scenario. This is why companies implement code review processes and testing teams.

I agree with some of this. I think this is a good attempt to transplant "blameless postmortem" culture to the individual level. Yes, don't assume the cause of the bug is you.

On the other hand, this blatantly a dangerous sweeping statement. There are many situations an apology is well deserved, specially if the apology is directed to someone directly affected (customers). Telling leadership to NEVER apologize is going too far.

I like to make it more fun - like an "oops, let's go squish those bugs" sort of thing.

Hard disagree - this is why people like smaller companies over bigger ones. If they see accountability and acknowledgement, it goes a v far way rather than big faceless corp that says "We will get back to you in 24 hours :) "

Whenever a customer of ours finds a bug my heart sinks. One thing that has helped developer velocity and has helped against regressions in our UI has been putting our components into Storybook (opensource tool) + hooking it up to Chromatic's snapshotting tool. Every pull request we have to approve changes to UI components before the PR can get merged