Saturday, November 21, 2026

Substitution

     A bacon-and-egg sandwich, except I was out of bacon and Tam had some jamón serrano that wanted used up.  I call it "Spanish decal ham," since it's usually sliced see-through thin, and you don't even want to think about the price of a whole leg of the stuff.  But pre-cut and packaged in small amounts, it's not too costly to enjoy occasionally.

     Fried in a little olive oil until the fat just starts to brown -- which is probably a barbarity for which I will be called out -- it's a delightful substitute for bacon in a breakfast sandwich or omelet.  Set it on paper towel to blot up the rendered fat and oil while you cook the egg.  A little goes a long way, but it's a delightful trip with toasted rye bread, good butter, a rich, orange-yolked egg and Swiss cheese.

Friday, November 20, 2026

Misheard

     When the first headlines came over the radio about how the Feds were going to "...blow up unstable bomb-making matériel in Iowa," I misheard the state as "Idaho" and thought to myself that some new batch of political fringe types had gotten themselves in trouble again.

     But no.  If only it were that simple.  The bomb-makers, a sober industrial-type operation, are working for the U. S. Army in the rolling hills and farm fields of Iowa, and they've been keeping a specific type of lead azide in storage under more-or-less stable conditions of temperature and humidity for a long, long time.  It's that last vairable that is the problem; a little lead azide, sealed away from any of the things it likes to get into trouble with (copper, for instance), is not such a big deal.  It's a detonator component, and the Army uses small amounts of it in all manner of things that blow up, but they keep 'em in stock for years, carry them around under battlefield conditions, and use 'em up, one way or another, before the "best by" date.

     It's when you have a great big tank or carboy of the stuff and it sits for years that it becomes problematic, no matter how careful you have been.  It dries out and crystalizes -- and becomes shock-sensitive.  Think of it as the large-scale version of the small-scale (not so small!) problem with decades-old picric acid turning up in college and some high school chemistry labs: stored wet, in a proper container, and (back in its day) used up in the course of a year or two, it wasn't considered a big deal, no more than all the other dangers of a chem lab (explosive, flammable and toxic, like so many other items in the lab).  But there came a time when it fell from frequent use, and the old 4-liter bottle of picric acid ended up at the back of a shelf, drying out, becoming more and more unhappy....  Most of them were found and removed in time, and properly disposed of before causing a fire or worse.  Okay, now size that up: there are sixty-eight barrels of lead azide, 9,700 pounds of the stuff, and the plant chemists say it's not a matter of if but when: it's going to blow up.  The explosion can happen under their control, or whenever the lead azide decides.  There are chemical disposal methods, but they're mostly used for small amounts under laboratory conditions.  This stuff going to go up.

     Nobody wants to be downwind of a plume of something with a lot of lead dust in it.

     Looking at the Iowa facility on Google Maps, it's a typical munitions plant: lots of wide-open-spaces, long low buildings with empty fields or berms between them, rail sidings and elevated pipes that run for miles, some storage bunkers and whatever you call the sheltered spots for checking that the product goes boom as specified (or are those bunkers, too?), fences with signs warning of a restricted Army facility; and it's got small towns on all sides of it and a good-sized city nearby.  Nobody in the immediate neighborhood is unaware of what they do there and many of them work inside.

     But very few of them expected lead-bearing dust borne on the winds.  They're worried about it -- and people farther away, along the line of the prevailing winds, are even more so.  The Army doesn't sound happy about it, either; while spokespeople have expressed confidence that the lead would be well-dispersed, the amount sifting down to earth would be below dangerous concentrations no matter what, the Army -- and the Federal government -- doesn't have a great history when it comes to always being right about such hazards.

     Meanwhile, the lead azide is still ticking, and there's no way to see its clock.  Either the Army can read the weather forecast, clutch their best rabbit's foot, roll the dice and pick their time, or the lead azide will make the call, and an upcoming cold snap is going to speed up the process that makes it likely to explode.  At present, the plan is to blow the stuff up on Monday, and they've already done what they can to limit the problems next door and downwind.  There isn't any better answer.

     Update: Better answer or not, environmental groups have filed a lawsuit and the court has delayed the explosion pending a decision on a preliminary injunction or stay.  No word from the lead azide, however, and we should all remember the military adage that "the enemy gets a vote" in determining the outcome of conflict.  Tick-tock.

Thursday, November 19, 2026

Gashouse Brunch

     Sometimes known as a "square egg," the classic gashouse egg is an egg fried in the center of a piece of bread with a hole cut in it, a little butter or margarine in the skillet.

     My version isn't square but more of an oval: I start with rye bread, and butter seasoned with freshly-ground black pepper, a little smoked paprika and some Herbes de Provence.  Make the hole in the bread with a suitably-sized water glass and set the disc removed aside.  The burner can be set pretty low.  Plop the bread into the melted butter and move it around a little until it has soaked up a uniform coating, then flip it over and break the egg into it, adding more butter if needed.

     Break the yolk or not, however you like it, and then tear up the bread disc into little bits, dropping them into the egg, until you run out of room for more.  I usually manage about half of it.  The remaining half or so can be fried in the skillet.

     Let it cook until it's firm enough to flip, then turn it, add a slice of cheese a little smaller than the bread, and do the same to the left-over half disc.  Once the cheese melts slightly, it's probably ready -- this takes a little judgment.  Don't let the egg get ahead of you!  Season to taste with whatever condiment you think might work -- spicy/tomato-y flavors work and a dab of good mustard might, too.

Wednesday, November 18, 2026

Too Slow!

      I was going to write more about the current crash-fest in computerized things, but the pundits have beaten me to it.  Short version: AI keeps finding vulnerabilities (or claiming to -- look, AI still tends to tell people what they want to hear), organizations keep trying to plug them, and, um.  Some of those fixes are boxes full of vibe-coded glitches.

     And why is that?  There's the real story: At the heart of many businesses, you will find old hardware, running software that is often even older, stuff written for operating systems and dead(ish) languages that ran on mainframes and the original "minicomputers," a six-foot rack or two of electronics, emulated on slightly newer (call it late DOS-era X86s or early Windows) hardware.  People who really, deeply get that kind of programming were never terribly common, truly gifted troubleshooters of it even less so, and one of the core talents was what chessplayers call "sitzfleisch:" the ability to park one's backside in a chair and concentrate on the task at hand for genuinely unreasonable amounts of time.  Who does that now?  Hardly anyone.  And a lot of the old code is patches on patches on fairly wild improvisations that let ancient systems hand data off to modern networks and get input from them.

     Sometimes trying to fix it breaks it.  And most of it is only still there because jacking up the enterprise it supports -- a bank, or a factory or a subway, etc. -- and driving a whole new, modern system in under it, while it's all running, is nearly impossible.  They're better off (at least for this quarter -- and for a publicly-traded company, they're not even supposed to be looking much farther ahead; government stuff can be even worse) just patching the patches, even when it coughs and falls over.  It turns out that beating a dead horse until it softens and stuffing it into a powered exoskeleton will work, especially if you don't mind the smell.

     "Whoa, Nelly?"  Better not.  Your paycheck is in that cart it is hauling, along with your airline tickets, your retirement savings and your Social Security.

Monday, November 16, 2026

Blue Moons And Jackpots

     I'm enjoying an omelet for brunch, filled with mushrooms, ham, Swiss cheese and shishito peppers.  My first bite came with a surprise: it was spicy!

     About one in twenty shishito peppers will have a nice degree of fire to it.  Maybe even fewer.  It's not overwhelming.  All of them have the other components of nice pepper flavor, sharper and less sweet than a bell pepper, but once in a blue moon, they've got a little extra.

     That's probably the best way to understand the FAA ground stop last Friday: they got an unexpectedly hot one.  They were lit up by a blue moon.

     There's been a lot of back and forth about Transportation Sean Duffy's various (and not especially coherent) public statements about what happened, and various kinds of criticism of him personally, and President Trump's appointments generally, but the reality is, who would you hire to swap put routers at your work, Sean Duffy or Pete Buttigieg? Maybe Elaine Chao?  If you said, "none of them," go to the head of the class.  That's a lumberjack/attorney/reality TV guy/politician, a politician/philosophy-politics-economics scholar/military officer and an economist.  What do they know from routers or data networks?  About as much as the average college graduate, if that. That's not their job.

     You've got to go down multiple levels, into the FAA, and then -- maybe -- the person who manages the subcontractor who built and maintains the network (L3Harris) knows enough about technology and their network to understand the explanation of how things went wrong.  When they did go wrong, there's evidence the plug got pulled early -- but as information percolated upward through management, every level reacted with caution and thus the ground stop.

     It having happened, Secretary Duffy is doing what Cabinet members often do, using the event to try to leverage some more money for his department.  Will more money cure the problem?  Even he admits any improvements will not be quick.

     It's a technological system with non-geek management, which is not unusual.  What make it unusual is that it's the national air traffic control system.  What makes it look foolish is, they were doing upgrades on a Friday.  I don't know about your employer, but mine instituted a "no technology changes on a Friday" rule years ago.  Maybe it looked routine to L3Harris.  I'll bet they stop treating them as routine from here forward, no matter what turns out to have been the cause.

Sunday, November 15, 2026

Another Fall Day

     And, feeling better, I did not immediately proceed to yard work.  I spend some time on furniture-building, a project that I hope will work with a commercially-made display cabinet.

     I have done a little work on fallen limbs, underbrush, etc. since the Great Stupid Back Mess, but only sparingly and with great caution.  I have to minimize how much bending and lifting I do; even a little bit of it has me aching the next day.

Saturday, November 14, 2026

Progress!

     After three days out sick and dizzy, I managed to bathe and visit the grocer's this afternoon.  Hooray, me!  It wasn't a very dramatic cold but it knocked me about flat.

Friday, November 13, 2026

So, How's That "Super Intelligence" Going?

     Gizmodo, 21 hours ago: "The FAA Is Rolling Out Its AI Air Traffic Tool Nationwide."
     FAA, 3:54 p.m.: Nationwide ground stop.  "All departing traffic should remain groundstopped until further notice." In other words, no end in sight.

     Microsoft, busily implementing AI, suffered a huge outage yesterday through today in many of its web-delivered services.

     At Microsoft, armies of technicians and engineers dug in and have largely got the services functioning again.  FAA has fewer people -- there's your lean, "running the government like a business" approach, in this case Earl's Discount Variety, where they have only one clerk on duty at a time, who also stocks shelves -- but I have no doubt they've got everyone with a clue hard at work solving the problem and they will eventually succeed.  Sorry about your vacation and that critical overnight air express shipment!

     There seems to be a common thread here, and you can expect more of it.  "A.I" as it presently exists is not up to doing critical tasks.  Hey, maybe it will be, some day.  It's pretty convincing to a lot of people right now.  But when put to the test, it keeps collapsing like air-whipped bullshit on a hot summer's day, so maybe -- just maybe -- we might want to wait and keep on playing with it in applications where it doesn't gum up great swathes of email or endanger air travel, air travelers, and all us people on the ground under airplane routes?  Or, I guess, we can wait until it really screws up and manages to kill a bunch of people, and live with the reaction.

     Oh mighty Googly AI, what is the "Butlerian Jihad?"

     Update: Here and elsewhere, some skeptics have said AI is unlikely to have been the cause of the FAA ground stop.  Secretary of Transportation Sean Duffy's statement is incoherent, pointing to outdated "analog communications systems" causing "data network overloads."  The most generous reading of this patent nonsense is that their links between ATC centers and radio transmission/reception sites* are presently using voice-over-IP, which is a relatively straightforward replacement for dedicated analog lines, and that the VOIP system shares the same (presumably secure and in some way isolated) data network as all the rest of the FAA comms -- radar info, the (originally) teletype system for notices to pilots, routing and scheduling comms and so on.  What might overload this?  As it happens, VOIP data usage is pretty steady; silence fills about as many bits as conversation.  The other data is likewise consistent.  The NOTAM system is busy and gets more so for spicy weather or high-traffic periods, but it's plain text, low bandwidth.  The ACARS system that texts with plane crews is a similarly light load.

     Hey, you know what would overload those data networks?  Starting up a big, fat, interconnected AI that is intended to sort out optimum traffic routings on the fly, and has to keep communicating internally as it shuffles things around!  It's a problem in the same class as playing chess with itself, a known heavy burn of computational horsepower, and high traffic if the information about the pieces on the board is scattered across an entire continent and constantly changing.

     I stand by my theory: managers pushed to get the shiny new AI claptrap up and running, and it ate up the available bandwidth and then started crowding out all the other traffic, crashing their nationwide network before anyone caught on.  VOIP would have been the next-largest user of bandwidth and got hit the hardest.  There's almost certainly not going to be any one place where some team of geeks gets a real-time visualization of the total network traffic, so it may have gummed up and been restarted more than once before they realized they were hosed, gave up and started trying to get the things they broke working again.

     Update 2: The Secretary is saying the excessive traffic and subsequent crash was caused by contractor L3Harris (a merger of defense contractor L3 and electronics conglomerate Harris), working to upgrade copper infrastructure to fiber-optic, and that they either installed "a bad switch" (not like a light switch -- more like a mini telephone exchange, but for data) or were incompetent.  Bear in mind that all the work has to be done while the system is up and running, since it operates 24/7; and that the older hardware used between the analog radio gear and data network makes it especially easy to screw up in ways that might spam the network.  So yes, it could be that.

     FAA went into the Trump Presidency with a geek shortage, and DOGE hit them hard.  This is not conducive to maximizing uptime on an aging system,  Start making changes and, oops, what happened?  
__________________
* With a very few exceptions for ACARS, the military (UHF) plus long-haul stuff (HF) over oceans and in the outback, aviation comms are line-of-sight amplitude-modulated VHF voice in one band stuck in between the high end of FM broadcasting and TV channel 7, using essentially the same system no matter where you fly. "Line of sight" can be a very long way when one end of the link is way, way up there where airliners fly, but it's not infinite and there's a whole network of ground stations bristling with antennas, variously used by various flavors of air traffic control.  It is indeed complex, and yes, it can go very wrong if changes are made incautiously.

Thursday, November 12, 2026

Happy Birthday, Doc Savage

     Or so Kenneth Robeson wrote: "An old notebook...entry: 'This thing started November 12, 1932.'"

     That gets a little complicated, given that "Robeson" never existed.  He was a house name at pulp publishers Street & Smith.  Lester Dent, who came close to being a Doc Savage character in real life,* wrote most of the stories. Dent, publisher Henry W. Ralston and editor John L. Nanovic came up with the character, his backstory and his associates, and presumably one of them made the actual notebook entry.

     Doc went on to hundreds of pulp-magazine adventures, a string of paperback reprints a generation later (when I found them), fan stories, new stories, incorporation into Philip Joe Farmer's "Wold Newton" family tree of fictional heroes, villains and superheroes, even more reprints and a remarkably awful George Pal film.

     And he may have had a real-world antecedent: Colonel Richard Henry Savage -- 19th-Century U. S. military officer, adventurer, world traveler and author of popular adventure and mystery novels. Or perhaps Colonel Savage was the model for Doc's father, Clark Savage, Sr. 
___________________
* Originally a telegrapher, he went on to become a private pilot, ham radio operator, amateur sailor on the high seas with his own boat, world traveler, pioneer of commercial aerial photography and inveterate gadgeteer.  Among other things.

Home, Sick

     I'm in Day Two of a cold that has me home and sleeping a lot.  I have named it "Tamaritis," in honor of the first known patient.  (She says she has no idea where it came from.  Possibly elfshot, or a gladhanding candidate for political office, which amounts to the same thing,)

     It is some kind of a respiratory bug.  Hers settled in her lungs.  Mine's gone after my sinuses so far, with some of my usual inner-ear symptoms like dizziness, disorientation and a decided tilt to either the universe or me, depending on one's point of view.  A constant for both of us is utterly vile chills, the kind of creeping coldness that nothing seems to mitigate.  It seems to search out the infected person's weak points.

     I have continued with salt-water gargles when my throat gets scratchy, honey-sweetened hot lemonade* (I used up all the lime concentrate and the honey's getting low) coffee† and chicken soup.  There's a microwave-pouch version of the latter that's pretty good.  Tonight is Trash Night, so I shall endeavor to persevere in doing my part by cleaning out the fridge and changing a couple of litter boxes.  You would not want me operating a motor vehicle at present.  I'm having a tough enough time navigating on my own two feet.
________________
* And not, I hasten to point out, hot-honey sweetened lemonade.  Who knows, it might help, but I shall put off that experiment until I think I really, really need it.
 
† No known therapeutic value but I wouldn't want to do without it.

Wednesday, November 11, 2026

It's Veteran's Day

     It's a day to remember the living, the people -- mostly regular working Joes and Janes -- who go and do the hard, often dull, occasionally dangerous jobs in the country's armed forces.

     Today is a day originally marked over a century ago by the people who thought they had just finished a horrific war that would end wars, a war that left scars twisting across Europe that in places have still not healed, and may not for centuries yet to come.

     What they did not know is that their war would be followed by others, even worse.  By a century of war.

     We're in a new century now, and war persists.  It chews up and spits out the people who put on their country's uniform, for long hours and low pay.  Spare them a thought.  Give them your thanks.  Their job is to stem the tide, to confront the horror and drudgery so that you and I don't have to.  It is a gift beyond price.

I Still Don't Trust The Future

     The recent impeachment effort is one of the reasons I'm unsure how much change we're going to see when Congress turns over in January like pond water.

     There were enough House Democrats in Washington and enough Republicans playing hooky that had they bothered to show up, they could have carried a vote to impeach Secretary of Defense Hegseth.

     On the other hand, there are not -- and will not be -- sufficient votes in the current Senate to actually oust the guy.  Nope; the Senate would have cleared their slates, shoved the furniture around to set up for the big event, made sure the Secretary and whatever legal counsel he had -- possibly Attorney General Todd Blanche himself -- were set up with carafes of water and coffee, comfy chairs and microphones, etc., let Senators do a little chastising of their opposite numbers, let the Dems chide the impeachee and the GOPpers congratulate him, broken for lunch, come back, held a vote finding him not guilty and been done in time for a nice supper, maybe even drinks before.  What's the point?  Setting a few more of my tax dollars on fire?

     They can run the process after the first of the year and maybe have a whisper of a chance of success, if the majority can find a handful of Senate Republicans minded to play along.  By then, the new minority party will have a better idea who they want to blame, and it might be him.

     This is all the old familiar song and dance, and if if I wanted to watch the same-old same-old done to perfection, I would have changed the channel to Bugs Bunny, who's got more panache and can carry a tune (Oh, that Mel Blanc and his successors and uncredited peers!).

     The Fed.gov has got a long way to go to earn my trust, no matter who's turning the crank.  I'm more inclined to let the Democrats finish their audition -- but make no mistake, it's indeed an audition.  I sure hope they've rehearsed!

     Around four this morning, I woke from a realistic dream in which I'd been out working in the front yard of Roseholme Cottage, the neighborhood looking even more haggard than it usually does this time of year, trees going bare, the vacant homes dark, the smashed house to the south a little more dilapidated, plumes of smoke rising in the distance, angled by the breeze.  A dark flying thing came burbling down from high in the gray and cloudy sky, small straight wings, big front tapering back to the tail, getting bigger and heading right for me!  I looked at it a little too long, figured it to hit to the south and ran around to the north side of house, yelling for Tam to take cover.  I curled up against the foundation as the drone missile impacted some distance away with a muted noise, shutting my eyes and wishing I'd told my parents I loved them more often.  The light got very bright red-yellow-orange even through my eyelids and I thought, "Is this really it? The fighting wasn't that bad! I wasn't supposed to end this way!" And then I woke up.

     Yeah, ask me how I feel about the future.  My subconscious knows.