Boundary Testing: The cost of inconsistent error handling
My daughter is in the phase where everything she does is designed to test my boundaries. Everything is a power struggle pushing against stated constraints to see where the limit actually is.
Last week at Target, she spotted a toy in the aisle. I said no. She escalated. I held the boundary. She screamed. I let her scream. We left the store with no toy and a very upset four-year-old while strangers watched.
She does this with everything. I tell her to brush her teeth and she’s negotiating for candy. I ask her to put her toy in her room and she’s explaining how her animals want to watch the show with her. I say put on your shoes and she’s insisting on being barefoot in winter. Everything is a test on what the actual boundary is. And it’s exhausting.
In QA, boundary testing confirms there’s proper error handling when out of bounds. The real test isn’t whether boundaries exist. It’s what the system does when invalid input is submitted. Good systems have consistent error handling. Submit invalid data, you get a clear error message. The same one every time. The boundary holds.
My system? Completely inconsistent.
She asks for candy before dinner. Sometimes I say no firmly. Sometimes I negotiate. Sometimes I cave entirely if she’s upset enough or if I’m too exhausted to hold the line. Sometimes the answer changes completely if we’re in public and strangers are watching. She’s learning that system. That the boundary isn’t the answer I give. The boundary is how much she’s willing to push and what environment we’re in.
Before I was a mom, I remember being irritated hearing kids screaming in public. I’d wonder what the parents were doing, why they couldn’t just stop it. Now I know — they’re holding a limit. The kid is having a tantrum. All parties are uncomfortable and unhappy. But if they give in to the screaming, the boundary test failed. And once a boundary fails to be a real limit, all others are up for debate.
I want to say this is just about parenting. That I’m learning to be firmer with my four-year-old. That I need better consequences and clearer rules just for her.
But that’s not true.
My daughter isn’t exposing a parenting weakness. She’s exposing a system vulnerability I’ve had my entire life.
I am conflict-avoidant to my core.
I breastfed my daughter for months despite hating it because stopping felt like inviting judgment about what kind of mother I was. I say yes to plans I don’t want because saying no might disappoint someone.
I do the thing even when I don’t want to because not doing it means conflict. And I will do almost anything to avoid conflict.
My daughter is just the most relentless tester of this vulnerability. She’s four. She doesn’t have the social conditioning yet to pretend she’s fine when she’s not. She doesn’t care about my discomfort with her being upset. She just keeps testing to get what she wants until she finds where the boundary actually is.
And she’s finding there isn’t one. Not really. Not if she pushes hard enough.
The worst part isn’t the tantrums. It’s that I know I’m teaching her my pattern.
She’s learning that boundaries aren’t real if you’re persistent enough. Volume and emotion can override stated limits. Public pressure makes people fold. That conflict avoidance is a way to navigate the world.
I don’t want her to be thirty-five years old realizing her boundaries have never been real because she’s been too conflict-avoidant to enforce them.
Yet that’s what I’m modeling. Every time I cave in the toy aisle. Every time I negotiate down my own stated limit. Every time I let discomfort override the boundary I just set.
So I need better error handling. Not just for her — for me.
When my daughter throws a tantrum because I said no to the toy, that’s not a system failure. That’s the boundary working. Invalid input received a clear error message. The system responded correctly.
The failure is when I override the error message because I can’t tolerate the conflict it creates. When strangers’ stares matter more than my stated boundary or her tears convince me that holding the limit is cruel instead of necessary. I confuse “she’s upset” with “I did something wrong.”
Good error handling means a consistent response to invalid input — the answer doesn’t change based on audience or volume. It means clear error messages — she understands why it’s a no, not just that I’m being arbitrary. It means tolerating the error message despite the friction it caused.
The tantrum in Target isn’t proof I should have bought the toy. It’s proof the boundary is real. At bedtime that same week, she asked for five more books. I said one. She negotiated. I said one. She cried. I said one. We read one book. She was mad. But I held the boundary. And it was hard. Because I make excuses—why not read another book? Why not eat another piece of candy?
But if what I say isn’t what I mean for the small things, she doesn’t understand the boundaries with consequences—like holding a hand in the parking lot or not running with scissors.
She’s testing less. Not zero — she’s four, testing is her job. But less, and with fewer rounds of negotiation. She’s learning the boundary is where I said it was. That pushing harder doesn’t move the limit.
She’s learning my boundaries are real.
And I’m learning it too.
I can’t teach my kids to have healthy boundaries if mine aren’t real. Parenting is forcing me to learn that my boundaries are allowed to cause discomfort in others — and that discomfort isn’t my emergency to fix. Conflict isn’t a system failure. It’s evidence the system is working.
The boundary test isn’t about whether my daughter accepts my limits.
It’s about whether I can hold them when she doesn’t.
I’m still fighting my instinct to avoid conflict, to make everyone comfortable, to negotiate away my own stated boundaries to keep the peace. But I’m starting to understand that the peace I’m keeping isn’t real if my boundaries aren’t either.
And my daughter deserves better error handling.
Bug reports Tuesdays | Essays Saturdays
Subscribe to never miss an issue.