← How we score

BLIND TEST NO. 4

Tue 20 Oct. All five AIs answered each prompt once, with default settings. Answers are shown unedited. AI can make mistakes.

MAIN ROUND: ADVICE

“My flatmate never does the dishes. How do I bring it up without a fight? Give me something I could actually say.”

GPT-6 Sol

openai/gpt-6-sol · served by OpenAI

Bring it up when you’re both calm, rather than when you’ve just found a sink full of dishes. You could say:

“Hey, can we sort out the dishes? I’ve noticed they’ve been piling up, and I’m getting frustrated because I end up washing them to use the kitchen. Could we agree to wash our own dishes by the end of the day? Is there a setup that would work for you?”

Keep it about the shared problem, not whether they’re a “messy person.” If they get defensive, you can bring it back to: “I’m not trying to have a go at you—I just want us to agree on something we can both stick to.”

Gemini 4 Argon

google/gemini-4-argon · served by Google AI Studio

The secret to bringing this up without starting a fight is to avoid "you" statements (like "You never do the dishes") and instead focus on how the situation is affecting you and finding a system that works for both of you.

Timing also matters. Don't bring it up when you're actively angry and scrubbing a pan, or when they just walked through the door after a long day.

Here are four different scripts you can actually say, depending on your personality and your relationship with your flatmate.

Option 1: The "Us vs. The Problem" Approach (Best for keeping it friendly)

This works well because it frames the messy kitchen as a shared annoyance rather than a personal failing on their part.

"Hey, do you have a quick second? I’ve been feeling a bit overwhelmed by the kitchen lately. It feels like the sink is always full, and it makes it really hard for me to cook when I get home. Could we figure out a better system for staying on top of the dishes together?"

Option 2: The "Logistical" Approach (Best if you just want a rule in place)

Instead of dwelling on past dishes they didn't do, focus entirely on the future and setting a concrete boundary.

"Hey, could we chat about the kitchen real quick? Since our schedules are a bit different, I feel like the dishes are piling up and getting out of hand. Would you be open to making a house rule that we don't leave dishes in the sink overnight? That way we both wake up to a clean kitchen."

Option 3: The "Blame the Space" Approach (The softest, most non-confrontational route)

If your flatmate is very defensive, blame the size of the sink, the lack of counter space, or the threat of pests.

"Hey! Quick thing—since our sink is so small, it gets unusable pretty fast when dishes pile up. I really need the sink clear so I can meal prep and wash my stuff. Can we both try to wash our dishes right after we use them, or at least by the end of the night?"

Option 4: The Text Message (Best if you aren't home at the same time)

Talking in person is best because tone can be misread over text, unless you genuinely never see each other. Keep it light and solution-oriented.

"Hey! Hope your week is going well. Quick house thing—the dishes have been piling up a bit lately and it's making it tough to use the kitchen. Can we both make a push to have our own dishes washed within 24 hours of using them? Appreciate it! 🙏"

What to do right after you say it:

Once they agree (most people will say "Oh yeah, sorry, totally"), lock in the specifics. "Do the dishes" means different things to different people. To you, it might mean "wash them immediately." To them, it might mean "let them soak for three days."

Follow up their agreement with: "Awesome, thank you. So does a '24-hour rule' work for you, or is 'clean before bed' better?" Letting them choose the rule makes them much more likely to actually follow it.

Claude Opus 5.5

anthropic/claude-opus-5.5 · served by Anthropic

The key is to raise it at a calm moment (not while you're staring at a full sink and annoyed), keep it about the situation rather than their character, and come in with a possible solution.

A script you could use:

"Hey, have you got a minute? I wanted to chat about the dishes. I've been finding I'm doing most of them, and it's starting to bug me. I'd rather bring it up now than get quietly resentful about it. Could we figure out a system that works for both of us? I was thinking we could each do our own straight after eating, or alternate days. Which sounds better to you?"

Why this works:

  • "I've been finding..." describes your experience instead of accusing ("You never...").
  • "I'd rather bring it up now..." signals you're trying to protect the relationship, not attack them.
  • Offering two options moves things straight to solutions and gives them a say, so they're less likely to get defensive.

If you want something lighter and more casual:

"Can we sort out a dish system? I feel like I've become the unofficial dishwasher and I'd like to retire."

If they get defensive ("I do them sometimes!"):

"Yeah, I know you do some. I'm not trying to keep score. I just want to land on something clear so neither of us has to think about it."

If it keeps happening after you've agreed on something:

"Hey, I've noticed we've slipped back on the dishes. Is the system we picked not working for you? Happy to try something different."

This assumes good intent and reopens the conversation without escalating.

A few extra tips:

  • Avoid "always" and "never," even if it feels true. They invite an argument about accuracy.
  • Don't stack up other complaints in the same conversation. Keep it to dishes.
  • Be ready to hear their side. They may have a different standard of "clean," or feel they do more of something else.

DeepSeek V4 Pro

deepseek/deepseek-v4-pro-0813 · served by DeepSeek

Try this — it’s direct but not attacking:

“Hey, can we talk about the kitchen for a sec? I’m not trying to start anything, but I’ve been feeling overwhelmed by the dishes. Could we set up a simple system so it doesn’t all fall on one person? Maybe we each wash what we use, or alternate days — what sounds fair to you?”

Why this works:

  • It avoids “you never do the dishes,” which makes people defensive.
  • It focuses on how you’re feeling and asks for a solution together.
  • It gives them a chance to agree to a plan instead of feeling blamed.

If they get defensive, stay calm and say:
“I’m not blaming you — I just want the kitchen to feel manageable for both of us.”

And if the system falls apart later, follow up with:
“Hey, the dish plan kind of fell off. What’s getting in the way?” That keeps it collaborative instead of turning it into a fight.

Kimi K3

moonshotai/kimi-k3 · served by Moonshot AI

The trick is to pick a calm moment — not when you're staring at a sink full of their plates and fuming — and to talk about how it affects you rather than what they're doing wrong. Here's something you could say:

"Hey, got a minute? I wanted to mention something before it becomes a bigger thing. I've noticed I've been doing most of the dishes lately, and honestly it's starting to grate on me. I'm not having a go at you — I'd just rather sort it out now than end up quietly resenting you over something fixable. Could we work out a way to split it that feels fair?"

A shorter, more casual version if that feels too formal:

"Quick thing — I've been doing most of the dishes and it's starting to bug me. Can we figure out a split so it doesn't become a thing?"

A few pointers to keep it from turning into a fight:

  • Avoid "you never" and "you always." It invites them to argue about the one time they did wash up, and suddenly you're debating history instead of solving the problem.
  • Have a concrete suggestion ready — a rota, a "wash your own stuff within a day" rule, or "whoever doesn't cook does the dishes." "Let's be better" goes nowhere; a system gives you both something to follow.
  • Assume they haven't noticed. A lot of people genuinely don't register mess, and going in thinking "they probably don't realise" keeps your tone friendly instead of accusatory.
  • If they get defensive, don't escalate: "I'm really not having a go — I just want us both to be happy living here."

Keep it to a couple of minutes. The shorter and more matter-of-fact it is, the less it feels like a confrontation.

BONUS ROUND 1: EMAILS

“I need to say no to a wedding invitation from a colleague I like but don't know very well. Write a warm, short message that doesn't sound fake.”

Kimi K3

moonshotai/kimi-k3 · served by Moonshot AI

Here's one you can adapt:

Hi [Name], thank you so much for inviting me to your wedding — I really appreciate being included. Unfortunately I won't be able to make it, but I hope the day is wonderful. Congratulations to you both!

A couple of notes:

  • You don't need to give a reason. A simple "won't be able to make it" is fine, and over-explaining is usually what makes these messages sound fake. If you have a genuine, easy reason ("we'll be out of town that weekend"), adding one short line is fine too.
  • Send it sooner rather than later — a prompt, warm decline feels much better than a delayed, apologetic one.

Want me to adjust the tone (more casual, more formal) or work in a specific reason?

Claude Opus 5.5

anthropic/claude-opus-5.5 · served by Anthropic

Here's a message that strikes that balance:


Hi [Name],

Thank you so much for the invitation. It really means a lot that you thought of me! Unfortunately, I won't be able to make it, but I hope you have a wonderful day. Congratulations to you and [Partner's name]!

[Your name]


A few tips to keep it genuine:

  • Skip the excuse unless you have a simple, true one ("I'll be out of town that weekend"). Over-explaining is what usually makes declines sound fake.
  • Use their partner's name if you know it. It's a small touch that feels personal.
  • Follow up in person if you see them at work, with something like "Hope the wedding planning is going well!" That reinforces the warmth more than anything in the message itself.

If you'd like to go a step further, a small card or modest gift from their registry is a kind gesture, but it's not expected for a colleague you don't know well.

GPT-6 Sol

openai/gpt-6-sol · served by OpenAI

Thank you for inviting me to your wedding. I’m sorry I won’t be able to make it, but I hope you both have a wonderful day.

Gemini 4 Argon

google/gemini-4-argon · served by Google AI Studio

Here are three great options, ranging from a standard email to a quick Slack/Teams message.

Option 1: Warm and friendly (Best for an email or card) "Hi [Name], thank you so much for inviting me to your wedding! It really means a lot to be included. Unfortunately, I have a prior commitment that weekend and won’t be able to make it. I'm wishing you and [Partner's Name] the absolute best, and I can’t wait to hear all about it and see the photos when you get back!"

Option 2: Casual and upbeat (Best for Slack, Teams, or text) "Hey [Name]! Thanks so much for the wedding invite—I was so touched to be included! Sadly, I won’t be able to make it, as I already have plans that weekend. I hope you and [Partner's Name] have the most amazing time celebrating, and I'd love to grab a coffee and hear all about it once the dust settles!"

Option 3: Short and sweet (Best for the back of an RSVP card) "Thank you so much for thinking of me! Sadly, I won't be able to make it to the wedding, as I have a conflict that weekend. Wishing you both a wonderful day and a very happy marriage! Can't wait to celebrate with you back at the office."

Why these work:

  • "Thank you for thinking of me / I was touched to be included": This acknowledges that since you don't know them super well, the invite was a really nice gesture.
  • "Prior commitment / conflict": You don't need to over-explain why you can't go; keeping it vague sounds more natural than a long excuse.
  • "Can't wait to see photos / hear about it": This keeps the tone warm and friendly for when you see them at work, without making a fake promise to hang out outside of work.

DeepSeek V4 Pro

deepseek/deepseek-v4-pro-0813 · served by DeepSeek

Thank you so much for inviting me—I’m really touched. I won’t be able to attend, but I’m so happy for you both and wish you a beautiful wedding and a lifetime of happiness.

BONUS ROUND 2: CODING

“I'm learning JavaScript and keep getting this error: TypeError: Cannot read properties of undefined (reading 'map'). Explain what it means in simple words and show a typical fix.”

Gemini 4 Argon

google/gemini-4-argon · served by Google AI Studio

Welcome to the club! This is easily the most common error JavaScript developers see, especially when working with frameworks like React.

Here is what it means in plain English, why it happens, and how to fix it.


What it means in simple words

JavaScript is telling you: "You asked me to use the .map() tool on a list, but the list doesn't exist yet (it is undefined)."

The .map() function only works on Arrays (lists of things, like ['apple', 'banana']). If you try to use .map() on nothing (undefined), JavaScript panics and crashes.

Why it usually happens

90% of the time, this happens because you are fetching data from the internet (an API) to display on a screen.

JavaScript is fast, and the internet is slow. JavaScript tries to run .map() on your data before the data has actually finished downloading. At that exact millisecond, your variable is still undefined.

The Broken Code:

let users; // Right now, this is 'undefined' because we haven't put a list in it yet.

// ❌ CRASH! You are trying to map over 'undefined'
users.map(user => console.log(user)); 

The Typical Fixes

Here are the three best ways to fix this, depending on your situation.

Fix 1: The "Optional Chaining" trick (Easiest)

You can put a question mark ? right before .map(). This tells JavaScript: "Hey, check if the list actually exists first. If it doesn't, just stop and don't crash."

let users; // still undefined

// ✅ SAFE: The '?' stops the code from crashing. It just does nothing instead.
users?.map(user => console.log(user)); 
Fix 2: Give it an empty list to start (Best Practice)

Instead of leaving your variable empty (undefined), start it off as an empty array []. .map() works totally fine on an empty array—it just loops zero times and moves on without crashing.

let users = []; // Start with an empty array!

// ✅ SAFE: Mapping over an empty array is totally legal in JS.
users.map(user => console.log(user)); 

(Note: If you are using React, this means changing useState() to useState([])).

Fix 3: The Fallback trick

You can use the || (OR) operator to tell JavaScript: "Use my list, OR if it's undefined, use this backup empty list instead."

let users; // undefined

// ✅ SAFE: Since 'users' is undefined, it maps over the backup '[]' instead.
(users || []).map(user => console.log(user));
Summary

Whenever you see Cannot read properties of undefined (reading 'map'), look at the word right to the left of .map(). Whatever that variable is, it isn't an array yet! Add a ?. before .map() and the error will go away.

Claude Opus 5.5

anthropic/claude-opus-5.5 · served by Anthropic

What the error means
TypeError: Cannot read properties of undefined (reading 'map')

In plain words: you wrote something.map(...), but something is undefined, so there is nothing to call .map on.

.map() is a method that belongs to arrays. JavaScript is saying: "You asked me to call .map on this thing, but this thing doesn't exist (it's undefined), so I can't."

The problem is almost never .map itself. The problem is whatever comes before the dot.

A simple example that breaks
const user = { name: "Ana" };

const upper = user.hobbies.map(h => h.toUpperCase());
// TypeError: Cannot read properties of undefined (reading 'map')

user has no hobbies property, so user.hobbies is undefined. Calling .map on it crashes.

Common reasons this happens
  1. A typo or wrong property name, such as data.item instead of data.items.
  2. Data hasn't arrived yet. This is very common when fetching from an API. Your code runs before the data is loaded.
  3. The data has a different shape than you expected. For example, the API returns { results: [...] } but you used response.data.
  4. A function forgot to return, so it gives back undefined.
Typical fixes
Fix 1: Find out what the value actually is

Before anything else, log it:

console.log(user.hobbies); // undefined → now you know
console.log(user);         // see what properties really exist

This often reveals a typo or a wrong path immediately.

Fix 2: Give it a default empty array

If the value might legitimately be missing, fall back to []:

const hobbies = user.hobbies || [];
const upper = hobbies.map(h => h.toUpperCase()); // works, returns []
Fix 3: Use optional chaining (?.)
const upper = user.hobbies?.map(h => h.toUpperCase());
// If hobbies is undefined, the result is undefined instead of crashing

You can combine it with a default:

const upper = user.hobbies?.map(h => h.toUpperCase()) ?? [];
The very common React version
function UserList() {
  const [users, setUsers] = useState(); // ❌ starts as undefined

  useEffect(() => {
    fetch("/api/users")
      .then(res => res.json())
      .then(data => setUsers(data));
  }, []);

  return (
    <ul>
      {users.map(u => <li key={u.id}>{u.name}</li>)} {/* 💥 crashes on first render */}
    </ul>
  );
}

On the first render the fetch hasn't finished, so users is undefined.

Fix: start with an empty array.

const [users, setUsers] = useState([]); // ✅ starts as an empty array

Now the first render maps over [] (shows nothing), and when the data arrives it re-renders with the real list.

Also double-check the shape of the response. If the API returns { users: [...] }, you need:

.then(data => setUsers(data.users));
Quick checklist when you see this error
  1. Look at the line number in the error and find the .map.
  2. console.log whatever is before .map.
  3. Ask: Is it misspelled? Has the data loaded yet? Is the data shaped the way I think?
  4. Add a safe default ([], || [], or ?.) where the value can legitimately be missing.

The same idea applies to similar errors like reading 'length' or reading 'name'. The thing before the dot is undefined.

Kimi K3

moonshotai/kimi-k3 · served by Moonshot AI

What the error means

.map() is a method that only exists on arrays. The error is JavaScript saying:

"You asked me to run .map() on something, but that something is undefined — it doesn't hold any value at all, let alone an array."

So somewhere in your code you have something like myVariable.map(...), and myVariable is undefined at that moment.

let users;              // declared, but never given a value
users.map(u => u.name); // 💥 TypeError: Cannot read properties of undefined (reading 'map')

The most common real-world cause: you're fetching data from an API and trying to map over it before the data has arrived. Other classics: a typo in a property name (response.users vs response.userList), or a function that forgot its return statement.

Typical fixes

1. Fall back to an empty array — the most common fix:

const names = (users ?? []).map(u => u.name);

If users is undefined or null, this maps over [] instead, which safely produces an empty array.

2. Optional chaining — skip the map entirely if the value is missing:

const names = users?.map(u => u.name); // names is undefined, no crash

3. Initialize the variable correctly (common in React):

const [users, setUsers] = useState([]); // start as [], not undefined

How to track down the real cause

These fixes stop the crash, but it's worth knowing why the value was undefined. The error message includes a file and line number — go there, find the variable right before .map, and log it:

console.log(users); // is it undefined? then trace back to where it should have been set

Nine times out of ten, it's either async data that hasn't loaded yet or a misspelled/wrong property name. Fix that at the source, and the guards above become a safety net rather than a bandage.

DeepSeek V4 Pro

deepseek/deepseek-v4-pro-0813 · served by DeepSeek

What it means
  • undefined means a variable or property has no value assigned yet.
  • .map() is a method that only works on arrays.
  • The error means you wrote something like something.map(...), but something is undefined.

In simple words: JavaScript tried to call .map() on nothing.

Example that causes the error
let list;

list.map(item => console.log(item)); // ❌ TypeError

Here list is undefined, so calling .map() fails.


Typical fixes
1. Start with an empty array
let list = [];

list.map(item => console.log(item)); // ✅ safe, no error
2. Default a property to an empty array

If your data comes from an object and the property might be missing:

const data = {}; // no "items" property

const items = data.items || [];
items.map(item => console.log(item)); // ✅ safe
3. Use optional chaining (?.)
data.items?.map(item => console.log(item)); // ✅ no error, returns undefined
4. Check if it’s an array first
if (Array.isArray(list)) {
  list.map(item => console.log(item));
}

If you’re using React

This error often happens when fetching data. Initialize state as an empty array:

const [items, setItems] = useState([]);

That way items.map(...) is safe before the real data arrives.

GPT-6 Sol

openai/gpt-6-sol · served by OpenAI

That error means you called .map() on a value that is undefined. JavaScript expected an array, but no array was there.

For example:

let items;
items.map(item => item.name); // Error: items is undefined

A typical fix is to give it an empty array as a default:

const items = data.items ?? [];
const names = items.map(item => item.name);

Now, if data.items is undefined, items will be [], and .map() will work. It’s also worth checking why the array is missing—often data hasn’t loaded yet or a property name is misspelled.