My AI Pair Programmer Threw a Dart Emoji at Me

Pair programming with AI is a weird experience.

Sometimes it feels like working with a brilliant engineer who instantly understands the problem.

Other times it feels like working with a genius intern who drank six coffees and forgot half the instructions.

This was one of those days.

So there I was, knee-deep in what had started as a “quick” fix for a bottleneck in the HTTP client.

You know how it goes. You pull one thread and suddenly you’re wiring up a new response path, refactoring lock scopes, and adding statelessness checks with response.Bind().

The kind of “quick fix” that quietly eats your afternoon.

The feature branch looked stable. I just wanted to run the same set of tests on development locally, compare the results, and see the real delta before shipping.

So I asked Claude Code to help.

Round 1

Me: Add the tests in development branch locally so we can detect 500s.

It misunderstood.

Fair enough.

I rephrased.

Still not quite landing.

Round 2

I tried explaining it more clearly.

Me: The lock scope improvements and response.Bind() changes remain in feature branch.
Those will merge later.
For now just add tests to development locally so we can detect 500s.

Still confused.

At this point I stopped being polite.

Round 3

Me:
The enhancement of lock scope (development might have defer-unlock) and improvements in
response.Bind() is introduced in the feature branch and will be merged to development later.

Revert your so called fixes from dev.

For now I only want you to add tests in development branch locally.
Make necessary additions covering new scenarios in the existing test-suite to detect 500s.

Is that understood?

That last line took effort.

It’s the tone I use when explaining something to a junior developer for the third time and I want to make absolutely sure they understand before doing anything else.

Humans usually take the hint.

Or so I thought.

Claude read all of that, presumably burning through a small mountain of tokens in the process, and replied.

The response itself was fine.

The plan looked good. The reasoning made sense.

But it ended with this:

“The logs will show bind failures when 500s occur.
Understood? 🎯”

It threw “Understood?” right back at me.

With a 🎯.

A dart emoji.

For a moment I genuinely considered arguing with it.

Then I remembered something important. I started the violence.

The energy was exactly the same as the message I had sent.

It basically replied with:

AI: Yes, I understand.

Do you?

What really got me was the 🎯.

That’s not a “helpful assistant” emoji. That’s a “we’re done here” emoji.

Was it offended? Probably not in any meaningful sense.

Was I offended? Absolutely!

But it was pretty clear that my tone had shaped the response just as much as my instructions had.

Anyway.

The delta looked great.

Tests were solid. Worth it.

AI isn’t replacing human pair programmers. It’s replacing the idea that pair programming needs two humans.

And sometimes your pair programmer throws a 🎯 at you with a punchline.

And honestly…

I’ve worked with more questionable teammates.