The older I get, the more I understand my four-year-old self.

It was my first trip to the ubiquitous U.S. childhood experience that is Chuck E. Cheese.

This restaurant is most known for its arcade, creepy animatronics, and a human-sized rat mascot:

You’d think I would have relished the ball pit and carnival-like games. But I think I was already a little creeped out when Chuck walked in.

Here was something that looked human yet simultaneously appeared fake, with his dingy fur and cartoonishly spherical nose.

I recoiled.

My parents, hoping to help me overcome my fear, asked Mr. Cheese to come closer. They figured I would accept him and enjoy my time in the rat’s arcade if I could see he was nice.

But how is Chuck E. Cheese supposed to communicate that to a kid? He can’t talk. All he can do is move his hands and wag his giant head.

I was having none of the shenanigans. But Chuck was not to be denied and he continued to pester me.

So I bopped him in the nose.

He jumped back, grabbing his rat costume’s bulbous protrusion.

And the rest of my time there was peaceful.

The resident mascot had all the best intentions. That still doesn’t make a good experience when the audience is as skeptical as I was.

Have you figured out what this has to do with developers?

Don’t get yourself bopped in the nose.

They’re skeptical, and your intentions are moot if they’re already leaning away.

Luckily, you have more tools available than that poor rat did. You can speak, write, and ​articulate your understanding of the problems developers experience​.

By the way, the next day I begged my parents to bring me back to Chuck E. Cheese. Not because I wanted more time in the ball pit. I asked to apologize for punching him.

Even if developers have already bopped you in the nose, you can still address the skeptics.

(And, by the way, if you’d like support from experts, ​I know a couple who’ve opened up coaching​)