Skip to main content

Integrating Kids and Life: Fishing and other Maneuvers

As six year-old No. Two and I lay in our tent dozing off I heard gunfire in the distance.  At first it was just a shot or two.  I convinced myself that it it in fact wasn’t gunfire; clearly it was just the state park’s caretaker plopping things into the bed of a pickup truck.  Afew more bangs burst out from a little further up the vallery from where our tent perched overlooking the Pecos River.  I wondered what goofballs were out shooting at dusk, but frankly since we were in New Mexico, it wasn’t really that uncommon of a thing.  I closed my eyes again only to hear bang bang bang bang bang bang bang bang a few moments later.  Not many people in NM have automatic weapons, so that was a bit odd.  Still, the sounds were coming from around the bend of the valley so I wasn’t too concerned.  I watched the moon of our tent’s mesh roof trying to slide back into sleep.



Then—Two and I both heard it this time—an ominous roar rolled in from the opposite direction down the valley.  The ground beneath us began to vibrate just a bit.  Finally, it occurred to me what was going on, I didn’t want him to miss it so I hollered at Two,  “Get up!  Watch!”

“What!?” Two popped up in his mummy bag.

“Look up, and watch!” I yelled over the now booming noise.

Suddenly, there it was.  The nose of an A10 zoomed toward us.  As the plane screamed by, not more than 50 feet overhead—now literally shaking the ground beneath our sleeping bags—we could see it’s silhouette studded with a few dim red flying lights, trailed by dull red glow of its jet engines’ tail pipes.  A moment later, it was gone; headed up the valley towards the earlier gunfire.  We’d just had a front and center seat for the New Mexico National Guard's night-fighting maneuver drills.  Both of us totally thrilled with the impromptu flyover, we chattered on about it for a bit before finally cuddling back in to our bags, slowly drifting off to sleep under the almost full moon.

The whole experience was grand!  Earlier in the day Two even caught a rainbow trout out of the Pecos.  And, I wouldn’t have been able to experience any of it, at least not nearly as fully, if I hadn’t thought to bring Two along with me on the trip.  I might not have even been in that part of the state if Two and I hadn’t taken the time to visit a family friend who made blankets for Two and each of his siblings when they were born.  I probably wouldn’t have gone fishing, and even if I’d seen the plane, who would I have shared it with?

I’m incredibly lucky to have a job that allows me to work remotely as long as I have an internet connection, so lots of the situations the kids and I have found ourselves in have wound up like this most recent trip.  But, even when the kids and I hangout around town, the time I take to figure out how to involve the gang is always worth it.

Back when I did laboratory work, I’d pick the kids up out of daycare on my way to the pipe supply store.  The first time we went, I thought it would be just something interesting for them to see, something new.  When we got there though, it turned out they had free popcorn and bar stools.  Three year-old No. One and (then) 1 year-old No. Two—Three hadn’t arrived yet--- sat around happily munching popcorn while I took care of the lab’s piping business.  Again, to perhaps overuse a phrase, it was grand!

I see a lot of questions on parenting forums about what a kid of this or that age will enjoy doing.  My answer is always: they’ll enjoy doing everything you do.  What I rarely think to add though is that everytime I’m able to take the kids, there’s a huge perk in it for me too: I have way more fun!



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. ...