Skip to main content

What We Did With Our Summer and Spring and Fall and Part of the Winter

 You may have noticed the blog went fairly quiet this year. We didn’t quit unschooling with the pandemic, but our picture of unschooling sure did change a lot. I’ll write more about that soon, but first, let me point you at some of the thing we were doing while I wasn’t writing.

The gang and I discovered a 1950’s radiosonde on the side of a mountain in New Mexico. We didn’t know what it was at first, but thanks to Dr. Alice Gorman, we were soon on our way to finding out via twitter

Dr. Gorman introduced us to a nearby space archaeologist at New Mexico State University, and we were off and running. A month or so later, the whole thing was written up at DesignNews along with a few other articles on related topics by John Blyler.

The Radiosonde Discovery

and

The Radiosonde Vacuum Tube

and

All About Space Archaeology

In the meantime, the gang—9 year-old Daize, 8 year-old Towser, and 5 year-old Tawnse—and I did an interview with the really cool people at the Feeling My Flo podcast, and with each other about periods. The article that led to the interview was from a conversation in a gas station the gang and I had a few years ago about tampons

Our really fun conversation can be found at 


I got to talk about our spring activities—camping on our way to New Mexico, then hanging out at a campground on the verge of being shutdown along with, (apparently), an FBI fugitive—on the super-cool Homeschool Coffee break podcast.


With unschooling being batted around as one of the most misused phrases of 2020, I was lucky enough to get to write an article about how we do unschooling at Mumforce.

And most recently, I got to do an interview with the Evil Witches Newsletter about you know.. Unschooling, and how the whole thing changed for us with the advent of the pandemic.

And that’s what we’ve been up to. I stopped writing here for awhile, but we kept right on doing our sort of unschooling.


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