My 2-year-old is a better negotiator than most lawyers (probably). He’s also, without the faintest idea he’s doing it, learning programming logic.
“If I eat meatball, then I can have more blueberries?”
Conditional statements come naturally at mealtimes. He doesn’t know it yet, but he’s programming me.
The Daily Algorithms
Every toddler negotiation runs on programming logic.
The Basic If-Then
“If I put on my shoes, then we go outside?”
A textbook conditional. Input (shoes) produces output (park). He’s working out that cause and effect aren’t just laws of nature – they’re parameters you can negotiate.
The AND Operator
“If I brush teeth AND pick up toys, then two stories?”
Two conditions at once. He’s combining requirements.
“If I lay down AND be quiet AND close my eyes, then another story?”
A three-condition function, delivered from a fully horizontal position.
The OR Logic
“I wear the dinosaur shirt OR the truck shirt?”
He’s offering options, understanding that either input lands on the same output (a dressed child). Then he levels up: “If dinosaur shirt, then green pants. If truck shirt, then blue pants.” Different inputs routed to different outputs – branching logic, in pajamas.
The Edge Cases
My favorite is when he finds the bugs in our logic.
Me: “If you don’t eat your fish, then you can’t have more crackers.”
Him: doesn’t eat fish
Him: “I don’t want more crackers. I want melon.”
He found the loophole. Our conditional never accounted for his ability to reject the whole premise – a small act of edge-case testing, and he’s winning.
Or this one:
Me: “If you eat your fish, then you can have melon.”
Him: takes one bite of fish
Him: “May I have melon now, please.”
One bite of fish for a full bowl of melon. He’s optimizing for maximum reward at minimum cost, and honestly, the math checks out.
Why This Matters
These aren’t cute moments that sort of resemble programming. This is the real thing. He’s practicing:
- Conditional logic: if X then Y
- Boolean operators: AND, OR, NOT
- Variables: different inputs produce different outputs
- Edge cases: what happens when the assumptions break
- Debugging: finding the flaws in a piece of logic
- Optimization: maximum reward for minimum effort
Every negotiation is a little program he’s writing in real time.
The Magic Question
When he negotiates now, I’ve started asking: “What’s your if-then?”
“If I drink water, then we go outside.”
“If I get dressed, then we play GCompris.”
“If I lay down, then Mama sings Twinkle Twinkle Little Star.”
He’s getting explicit about his own logic. He’s learning that clear conditions lead to predictable outcomes – which is most of what makes a negotiation, or a program, actually work.
Your Turn
Tomorrow, when your toddler starts negotiating, listen for the logic underneath:
- What conditions are they setting?
- What operators are they using?
- Where are the edge cases?
Talk through each one (in toddler terms) and make it explicit. Then try this: “Okay, if we do that, then what do you want to happen?”
Watch them think. Watch them structure the argument. Watch them debug their own logic when it doesn’t hold.
They’re not just negotiating. They’re reasoning clearly about cause and effect, actions and consequences, effort and reward – the same habit of mind that makes good code, and a fair chunk of a good life.
This morning: “If I hug, then Mama is happy.” Yes, buddy. That program runs perfectly every time. What’s your favorite toddler if-then – the one that just melts you?