Apparently asking chatbots to name things they know about you that you never told them is A Thing on social media. I don’t really do social media — a chatbot had to tell me this was a thing — but I caught it in Sunday’s Seattle Times.
So I gave it a whirl, with a twist. I use ChatGPT for personal stuff — mostly DIY — and Claude for my paycheck. Two chatbots, two completely separate halves of my life, zero shared inputs. I ran the same prompts on both to see whether they’d describe the same person from opposite ends. Then I had Claude compare the two.
The agreement was the interesting part. When two models that know nothing about each other’s evidence land on the same trait, it’s probably real — not a quirk of how I talk to one of them.
Where they converged — the traits I’d trust
Explore aggressively, commit carefully. From wiring a detached garage and concrete pours on one side, from software safeguards on the other, both landed on the same instinct: I’ll investigate anything, but I get conservative the moment a decision is hard to reverse. Both flagged this as the most load-bearing trait.
I commit to models, not instructions. Neither model could get me to accept “do X” without “why X.” Give me the reason and the constraint and I move fast; give me a bare instruction and I stall. Advice only becomes useful once I understand it well enough to disagree with it.
Risk tolerance depends on the domain, not my mood. Risk neutral when failure means “well, that didn’t work”; averse when failure is expensive, dangerous, or irreversible. Identical finding from building a deck and from building data pipelines. One model put it best: I’m not a high-risk person, I’m a high-agency person — and those look similar from the outside.
Allergic to bad value, not to spending. I’ll happily spend real money when it buys something real, and a needless small expense genuinely irritates me. ChatGPT spotted it in a $190 used tool I was delighted by versus a $500 new one that seemed absurd. Claude had no evidence, but predicted the same thing from my work habits.
I think out loud to think at all. Both noticed I use the conversation itself as working memory — expecting earlier decisions to stay part of the picture, reconstructing the current state rather than holding it in my head.
I argue by provocation. I’ll float a slightly provocative “why not…?” not because I’m attached to it, but to see what survives criticism. Both models clocked it independently.
Impatient with ceremony. Once I understand something, I want to go do it. Process whose only justification is “it’s the process” wears on me fast.
I can admit ignorance without it stinging. “What’s this thing called?” sitting comfortably next to a detailed technical discussion five minutes later.
The unflattering half — both models agreed here too
The agreement wasn’t all flattering, and I’d be cheating to only post the good parts.
Impatience — this was the loudest one, and oh it’s real. Both models nailed it from opposite directions. I explore patiently, but I have almost no tolerance for process that exists only because it’s the process, or for explanations that ignore the actual situation in front of me. Here’s the part I admitted mid-conversation: at work I have to hold it in, because when I can’t it has a cost with other people — so the impatience comes out full-force on the chatbot, where it’s free. One model caught the tell before I said it: under stress I don’t get visibly frazzled, I just start moving faster, and I may not notice I’m stressed until it surfaces as impatience. If I seem to be pushing the pace, I am.
I mistake understanding for done. The moment I figure out how something works, my estimate of the effort left collapses. ChatGPT put it perfectly: that’s how a person ends up standing next to four 6″x6″x8′ pressured treated posts thinking, “oh — these are really fucking heavy. How am I going to move these?” The insight is the easy part; the commitment, the timeline, the actual weight show up later. The non-lumber version of this has cost people in my life real time.
I can confuse building the system with making progress. Setting up the structure feels like doing the work. Sometimes it is. Sometimes it’s a very productive-looking way to avoid just doing the messy thing once.
Where they diverged — the more interesting part
Confidence vs. compensation. Both saw that I hold my technical skill loosely — happy to say “I don’t know.” But ChatGPT, looking at my hobbies, read it as pure healthy comfort. Claude, looking at my work, read it as partly compensating for a doubt about belonging, about not having a CS degree. Both are right, and the gap explains itself: nobody grades my carpentry credentials, so at home I’m genuinely free — but in my profession the same modesty carries a charge, because that’s where my identity is on the line.
Aesthetics. ChatGPT found a strong streak I care about — proportion, coherence, whether something looks intentional. Claude had zero evidence of it from code, except it’s the same instinct behind how carefully I name things and my refusal of clever-but-opaque shortcuts. The design brain and the systems brain turned out to be the same brain; one model just couldn’t see that face of it.
Why I build at all. ChatGPT said I DIY because solving the problem is the fun — hiring it out would remove the interesting part. Claude said I build partly to discharge stress and stay in control. Neither is wrong, and that’s the point: building is simultaneously how I have fun and how I manage anxiety, which makes it genuinely hard for me to tell which one I’m doing at any given moment.
The one thing neither could see
Both models describe someone who takes systems apart until they stop being mysterious. Neither could tell whether people fall into that category for me — whether I run the same “interrogate until it makes sense” process on relationships, or whether that’s the one system I’ve decided doesn’t yield to it. That’s the honest edge of the whole experiment: two AIs modeled my relationship to systems with startling agreement, and neither has any idea what I’m like with the things that won’t be taken apart.
How I think I’ll use this
My next job, I think I’ll share two strengths and two weaknesses about me:
- Strength — High-agency, not high-risk. I take on things that look risky to others because I’ve broken the risk into parts I can control. Give me a hard, multi-skill problem and I’ll go deep; give me the same payoff riding on luck and I’ll pass. I move fast once I understand the system.
- Strength — I commit to models, not instructions. Tell me why, not just what, and I’ll run with it — and catch inconsistencies you didn’t know were there. Advice lands once I understand it well enough to disagree with it. I’ll change my mind instantly for a better argument.
- Weakness — Impatient, and it’s the tell. I explore patiently but I’m quick to frustration with process-for-its-own-sake or explanations that ignore the actual situation. Under load it shows up as accelerated doing, not visible stress. If I seem to be pushing pace, I probably am — flag it.
- Weakness — I mistake understanding for done. The moment the mechanism clicks, my estimate of the remaining effort collapses — and the heavy part (the commitment, the timeline, the human cost) shows up later. Hold me to the finish, not the insight.