Skip to main content

On the Value of Speaking Respectfully

Mom-person bolted across the street for the train.  If she got her foot in the door, we'd all get in.  If not, we'd stand out in the cold for another 20 minutes or so. 

 No. 1, our five year old, bolted with her.  She's big enough to keep up now, and did so admirably.  Her more frequent strides matched her mom's; she stayed right beside her; she was safe.  I'd picked up No.3, our youngest.  She was OK with the development, more bemused than anything else, but also safe.  Then, there was No. 2.  At three years old, he couldn't quite keep up with Mom-person.  She was three quarters of the way across the street before he thought to move.  I cringed.  We'd done this before.  I knew from experience that a few seconds delay could radically change the traffic situation.

Whereas there were no cars when mom-person leaped, there very well might be now.  For slow-twitch participants, like No. 2 and myself, the whole transaction required another scan of oncoming cars.  The issue was No. 2 didn't know that.  He crouched to leap, exactly as I knew he would.  I inhaled a fresh lungful of air preparing to resort to the technique I'd used every time before.  His legs began to uncoil into a powerful jump, I yelled in a forceful, determined voice, "Stop!"

Then, No. 2 and I played out a familiar routine exactly as we had dozens of times before.  He stopped.  He was safe.  As I scanned for cars, No. 2 screamed, and started to cry.  It's what I'd known would happen the instant I saw Mom-person leap for the train.  I'd cringed, accepted my fate, and kept everyone safe.

Later that night, lying in No. 2's bed for our good night snuggles, I asked him if he'd had a good day.  His response was characteristically honest, "No."  I asked why not, and No. 2 replied, "Dad, you made me cry."

"When I yelled at you at the train stop?" I asked.

"Yeah."

"Do you know why I did it?" I asked.

"No," 2's plaintive voice came out of the darkness..

"I was worried you were going to get hit by a car I didn't know about.  I had to make sure you were safe.  I needed you to stop right away, so I yelled.  I'm sorry buddy."

I heard a small sniffle followed by "I don't like it when you yell.  It makes me sad."

"OK," I said, "let's work on a plan.  When Mom runs for buses or trains, you stay right with me.  I'll try to warn you before she's going to do it, but no matter what, you stay with me.  Then, next time, I won't have to yell.  Sound good?  Can you do that?"

"I can."

A few days later, standing across the street from our train, I could see what was likely to happen, and I calmly got No. 2's attention, "Mom's going to bolt.  You're going to hang with me right?  Then we'll catch her when I say it's safe, OK?"

"OK Dad."

Annnnnd, we haven't had a problem since, well, you know, not with that anyway.

I was inspired to share by the WSJ article by Jennifer Lehr, "The Wrong Way to Speak to Children".  Ms. Lehr suggests that parents speak respectfully to kids as if they were adults.  She has written an entire book on related subjects called Parentspeak.  It's due out in three days on January tenth.

The comments on Ms. Lehr's article are intense, and in both directions; a lot of parents love their children intensely.  I think that's good.  As for me, when I can remember to do it, and when the situation allows it, (obviously I don't always remember, and when I don't, the timing's not usually right either), talking with the kids in the way Ms. Lehr suggests opens up a new world, and makes life easier for all of us.  I get a window into what and how the kids think, and they get to see my perspective on why we do the things we do.  It's good; we're building a relationship... you know, just like grown-ups.






Comments

Popular posts from this blog

How Many Files Can You Add to a GPT Project? An Interview with GPT-5 on Limits, Context Engineering Tips, and Chats

 Setting the scene: I’m tinkering with Project TouCans, knee-deep in radio logs, SQLite dumps, and Cesium code. Naturally, I’m wondering if shoving all this into one GPT Project is a recipe for brilliance… or for disaster. So I turn to Vril — you know, after Brainy from the Legion of Super-Heroes , because what else do you call your AI sidekick who always has the answers? Time to ask him straight up. [ As an aside, yes, GPT-5 has decided to sometimes call me Vail. I'm not sure why to be honest. Also, I asked Vril, er GPT-5, to write up our interview for me. Apparently, me asking it to 'Bro' up a few stories, just for fun, has convinced Vril that I use 'Like,' more than I actually might. ] Me (Vail): So Vril, how many files can I throw into a GPT Project before it just starts choking? Like, is there some magic number where the context window taps out and everything falls apart? GPT-5 (Vril): Great question. There’s no single hard file limit. What matters is ...

The Alcubierre Warp Drive Tophat Function and Open Science with Sage

I transferred yesterday's Mathematica file with the Alcubierre warp drive[2] line element and space curvature calculations to the  +Sage Mathematical Software System  today, (the files been  added to the public repository [3]).  If you haven't used Sage before, it's a Python based software package that's similar in functionality to Mathematica.  Oh, and it' free.  I also worked a little more on understanding the theory, but frankly, I made far more progress with the software than the theory.  What follows will be a little more of the Alcubierre theory, plus, a cool Sage interactive demo of one of the Alcubierre functions[1], as well as a bit about my first experience with using Sage. Theory The theory is fun, but it's moving slowly.  Here's the chalk board from this morning's discussion Alcubierre setup the derivation using something called the 3+1 formalism which means we consider space to be flat, (in this case), slices that are labelled ...

When Codex CLI Met Port 9 (Debugging WinError 10061 in a Whisper Pipeline)

When Port 9 Ate My Transcript When Port 9 Ate My Transcript A small debugging story about proxies, Codex CLI, and why localhost isn’t always your friend. CopaseticFlow field notes WinError 10061 Codex CLI + Whisper Environment gremlins There’s a particular kind of bug that feels like someone's been messing with your network stack again. You run a script from cmd.exe . It works. You run the exact same script from Codex CLI. It stops with: [WinError 10061] No connection could be made because the target machine actively refused it FFmpeg happily splits the audio. The Whisper API call dies immediately. No 401. No timeout. Just an instant refusal. Translation: that’s not an API error. That’s a socket being rejected. ...