Bugs, Blame, and Shame

Way back in the garden, Adam and Eve started a game that we continue to play. We all know how to play it. I see my kids do it all the time. That game is the blame game.

Deeply ingrained in the culture of programming is to blame. 

• We blame the author of the code.

• We blame the user for "using it wrong."

• We blame Q.A. for reporting the problem.

• We blame the platform.

• We blame the hardware.

• We blame our tools.

Blame is so prevalent in programming that some of our tools even have a "blame feature" built-in. 

Tightly coupled to blame is the feeling of shame. Blame creates shame, or at least that's its intention. It's not trying to point out an error in a loving way. It wants to grab hold of the spotlight and shine it on the guilty.

For some personality types, such as Type One, the external shaming is nothing compared to the words they have for themselves. My wife is in this camp, and she heeps condemnation on herself any time she fails to meet her high standards. It breaks my heart.

Sadly, the use of blame and shame doesn't get us any closer to accomplishing our goals. In my experience, they stop all forward momentum and create a hostile atmosphere for the team. Which destroys morale, kills trust, and negatively shapes the stories we tell ourselves about our worth and identity.

What I love about Jesus is that He didn't blame or shame people for their mistakes. He had all kinds of opportunities to do it, too, like with Zacchaeus, or with the woman caught in adultery, or when Peter disowned him three times.

As believers, we have an opportunity to change the tone and culture around bugs. We can diffuse these emotionally charged moments and inject the fruit of the Spirit—love, joy, peace, patience, kindness, goodness, faithfulness, gentleness, and self-control. We can be the encouragers that our teams desperately need. We can lead with love.