I was a kid during the glory days of the Apollo space program and as you’ve probably heard me say a million times, Dad took us to Florida to see the actual launch of Apollo XI. Like every kid I lived and breathed every aspect of the Mercury, Gemini and Apollo missions, and I’ve devoured every book and movie I can find about it. “Apollo 13”? Loved it. “From the Earth to the Moon”? Terrific. “The Right Stuff” ? Fabulous.

That’s a picture I personally took of the Apollo XI launch on July 16, 1969.

But, For All Mankind, WOW.

I need you to watch this too. Sign up for a free trial of Apple TV+ if you have to (i’m biased, but it’s a great service.)

This is a fictional TV series (on Apple TV, about to enter Season 2) from Ronald D. Moore, the creator of “Battlestar Galactica” that’s an alternate-history view of the world, starting in 1969 as the first Apollo missions are set to land on the moon, except … the Russians get there first. All told from the point of view of the NASA astronauts and engineers – and their families! – who are suddenly behind, racing to catch up.

I just love this show. It’s alternate history that feels real.
The thing is, I seem to be surrounded by increasing numbers of people younger than me, who weren’t around when this was all happening, and who might be unaware of exactly what went down. I don’t want them to be puzzled by For All Mankind. I want them to revel in it too!

This article’s for you.

Of course the Russians never actually landed on the moon, but as a kid I remember people being worried that they’d do something to upstage the Apollo XI landing. And – that’s what happens in episode 1. The first man lands on the moon, and it’s NOT Neil Armstrong, it’s Alexei Leonov.

This, of course, gets NASA and the American government all riled up, and the space race is ON. The show starts to diverge from reality as the Americans scramble to get Neil Armstrong and Buzz Aldrin to the moon, but now shortly thereafter, the Russians have landed their second ship, and – it’s a woman. NASA now scrambles at President Nixon’s direction to recruit and train female astronauts.

I don’t want to give too much away, but the women astronauts and engineers are the true heroes of this alternate version of the space race.

What truly fascinates me about this show is the mixture of fictional and real people and events.
For instance, the Russians have never actually landed anybody on the Moon, but Alexei Leonov was a real cosmonaut, the first person to walk in space outside the capsule, and he really had been scheduled to be the first Russian on the moon.

We see a variety of actual people – NASA astronauts, administrators, politicians and so on, in slightly modified roles as the show’s timeline begins to diverge from reality. Here for instance are some notes on a few REAL people or events, what they did in real life, and what happens to them on the show.

(It’s also fascinating watching the technology slowly get better – very primitive computers and displays at Mission Control in early episodes, much better computers towards the end. That’s a reminder of how much of what NASA did drove advances in civilian technology too. Imagine if we’d kept going to the moon in real life, not just in the show.)

Also somebody gives somebody a slide rule. I liked that.

the actual Apollo missions

Apollo missions used a three-astronaut crew; two would descend to the lunar surface in the Lunar Module, while the third orbited the moon in the Command Module for a few days waiting for the crewmates to return in the (top half of the) Lunar Module. They’d rendesvous, everybody would transfer back into the Command Module, and they’d leave lunar orbit and head back to Earth.

A few missions were just rehearsals for different aspects of the mission.

Mission	Purpose
Apollo 1	A test, on the ground, that tragically ended in a fire, killing astronauts Gus Grissom, Ed White and Roger Chaffee. This was a major setback to the Apollo program, and NASA had to regroup.

Apollo 2,3|There were a variety of test launches but these names weren’t used.

Apollo 4 | An uncrewed launch, the first est of the Saturn V launch vehicle. 3 earth orbits.

Apollo 5 | An uncrewed launch, the first flight to include a Lunar Module. 7 earth orbits

Apollo 6 | An uncrewed launch. 3 earth orbits.

Apollo 7 | The first Apollo mission to fly with a crew of 3 – but only to earth orbit, testing various systems.

Apollo 8 | The first astronauts to leave Earth’s orbit. Apollo 8 executed the trans-lunar injection burn, and headed for the moon. It orbited the moon several times, took some very famous photographs, and returned to earth. The Lunar Module was not involved this time.

Apollo 9 | Earth orbit, but with the Lunar Module on board and the team practiced docking and undocking manouvres.

Apollo 10 | A full on dress rehearsal for a moon landing. Apollo 10 flew to the moon, where the Lunar Module separated from the Command Module and descended close to the surface – without landing.

Apollo 11 | Neil Armstrong and Buzz Aldrin become the first astronauts to walk on the moon’s surface in July 1969, while Michael Collins orbited above in the command module.

Apollo 12 | Yet another moon landing, a successful mission in the mold of Apollo 11, but to a different part of the moon, which I should really look up.

Apollo 13 | Houston, we have a problem. I hope you’ve seen the movie Apollo 13 which is an excellent dramatization of this real-life accident. The crew went to the moon, orbited a few times but were obviously unable to land due to damage from an explosion in the Service Module, and due to heroic efforts of many at NASA, they returned safely to the earth.

Apollo 14 | A two day visit to the moon, including Alan Shepard, who was already famous as the first American in space on the first Mercury mission.

Apollo 15 | They took a CAR to the moon on this one! The first launch that included the Lunar Roving Vehicle.

Apollo 16 | Three days on the moon, with the LRV. Commanded by John Young, later the commander of the first Space Shuttle launch.

Apollo 17 | In December 1972, Gene Cernan became the last person to walk on the moon.

And that was it. Cernan died in 2017. Only twelve astronauts have ever walked on the moon. As of this writing, only Buzz Aldrin (Apollo 11), David Scott (Apollo 15), Charles Duke (Apollo 16) and Harrison Schmitt (Apollo 17) are still with us. Schmitt is the youngest, at 85.

We haven’t been back. We thought there’d be more – but almost 50 years later, nobody has returned to the moon.

Well, not in real life, anyway.

But on the show …

Apollo 10

This really was a manned mission to the moon – but without a landing. The plan – which we also see in the show – was to rehearse every step of the Apollo XI mission, EXCEPT the actual landing. In reality, astronauts Tom Stafford and Gene Cernan descended in the Lunar Module to within 8 miles of the moon’s surface, at which point they deliberately “aborted” the landing and returned to join the Command Module (and astronaut John Young) and return to Earth.

In the show, it’s more or less the same except Apollo X is crewed by (fictional) Ed Baldwin and Gordo Stevens, who become major characters throughout the rest of season 1, and the “aborted” landing becomes quite the plot point as people question if they SHOULD have gone ahead and landed, and beaten the Russians.

Apollo 11

Of course this mission actually went to the moon, but on the TV series, they will be the second people to get there. One of my favourite scenes in the show shows a technician crawling into the craft while it’s still on the launchpad, to remove the historic plaque that was attached the leg of the lunar module. You know, the famous REAL plaque that said “Here men from the Planet Earth first set foot upon the moon. We came in peace for all mankind.”

This is the real plaque, still there today on the Sea of Tranquility.

And on the show, well, they’re suddenly not going to be first any more. Better remove the plaque before launch. A great little detail.

Neil Armstrong, and Buzz Aldrin

Armstrong and Aldrin are, of course, the first two people to land on the moon. In the show, they’re beaten to the moon by Alexei Leonov, but they still land as scheduled in Apollo XI – with a major twist, that I won’t spoil here.

Michael Collins

In real life, command module pilot on Apollo XI, so he orbited the moon while Armstrong and Alrdin landed.
In the show, he returns as the commander of Apollo 23.

Wernher von Braun

von Braun was a major figure in real-NASA – an actual Nazi Germany rocket scientist who moved to the USA and was instrumental as director of the Marshall Space Flight Center and chief architect of the Saturn V rocket. In real life, he was also obviously quite controversial because of his Nazi background. Tom Lehrer wrote a famous song about Von Braun and his controversial past.)

In the show, von Braun is played by noted Canadian actor Colm Feore and … well, his Nazi background is still a problem, and that affects the arc of the show.

The Mercury 13

In the show, President Nixon angrily orders NASA to recruit some female astronauts to help win the PR war – and many of those astronauts have spectacular roles later in the show.

In reality, a group of women known as the Mercury 13 were recruited and went through the same training as the actual Mercury astronauts, although they weren’t formally part of the space program. One of them was an accomplished pilot named Jerrie Cobb. In the show, this group is brought back into the space program and somewhat controversially brought up to speed – and one of the successful astronauts and a major character from this group is named Mollie Cobb, no doubt as an homage of sorts. (and now that I’ve done a little more googling, the producers agree that they named Mollie as a tribute to Jerrie Cobb who died during the production of Season 1.)

Deke Slayton

Real Donald K. “Deke” Slayton was one of the original Mercury 7 astronauts, whose career was derailed by a heart issue that meant he couldn’t fly in the Mercury program, and he became a senior NASA administrator and manager of the astronaut office.
He was eventually cleared to fly, and flew on the Apollo-Soyuz mission (a joint earth orbit thing between American and Russian spacecraft) and here he is, whaddya know, with cosmonaut Alexei Leonov. (See above! In the show Leonov is the first man on the moon.)

Deke Slayton is a major character in the show too, with a gritty performance by actor Chris Bauer. He’s in the same role as manager of the Astronaut office, selecting crews and … whaddya know, he manages to insert himself into the crew on one of the moon missions later in the show.

Real Deke Slayton passed away in 1993. I am very curious to know what his family thinks of his portrayal on the show.

Gene Kranz

Real NASA flight director. If you saw the movie Apollo 13, you saw a gritty portrayal of him by Ed Harris, chewing the scenery, and barking out the famous line Failure is not an option.. He never actually used that term but he was still a heroic real NASA character.

In the show, he’s played by actor Eric Ladin in the same gritty style.
You’ll want to watch carefully as he inspects the (mythical) Apollo 23 pre-launch. It doesn’t end well.

President Kennedy

Lots of fun historical tidbits are dropped in the show. You hear that Senator Ted Kennedy has postponed a vacation on Chappaquiddick to deal with some crisis or other – of course, in reality, he really did go to Chappaquiddick and an incident there derailed his political career.

On the show however – no incident! And he’s President by the end of the season, although we never really see him in the show.

Moon Missions

The actual Apollo program landed Apollos 11, 12, 14, 15, 16, and 17 on the moon between 1969 and 1972, with a famous accident on Apollo 13. Future missions, including Apollos 18 and 19, were scrapped, and today you can see some of that actual launch-ready hardware on display at the Kennedy Space Station.

Here’s some of the remains of the unused Apollo 18, 19 and other hardware on display today – we visited the Kennedy Space Center in 2015 and I highly recommend this tour. These aren’t museum mockups – this is actual launch-ready hardware that was built and never used. You can’t help but feel embarrassed that this magnificent vehicle is on display in a museum and never launched.

For All Mankind is moving at a much faster pace, due to competition with the Russians. At one point it abruptly fast-forwards by two years, to keep the plot moving along, and by the mid-1970s, NASA has an actual permanent base on the moon (and, minor spoiler, so do the Russians.) By the end of Season one, Apollos 24 and 25 are launched. And, NASA has modified the moon landing hardware so that the lunar module isn’t a single use land-once take-off-once thing as it was in reality, but a reusable vehicle to take people from lunar orbit to the surface. The tech still seems very believable and the Jamestown moon base is really fun to see, imagining that you’re still in 1975.

There is one hell of a cliffhanger involving an accident between fictional Apollos 24 and 25 at the end of episode 9, which turned out to be one of the most gripping things I’ve ever seen on TV.

And watch the final episode right past the credits. There’s a post-credit flash-forward to 1983, where we see NASA launching the Sea Dragon, a massive rocket launched from the middle of the ocean. Of course we’re now solidly in the fiction realm, but the Sea Dragon was an actual idea NASA was kicking around in the early 1960s (and one you briefly hear Von Braun mention on the show.)

What’s up in Season 2?

A first look is out.
We see modified space shuttles heading towards the moon.
We see a disturbing escalation of military action on the moon’s surface – astronauts with weapons.

And, I hear we’re going to see the Buran, the fabled Russian shuttle. In reality, the Russians were copying the overall design of the US shuttle but theirs never made it to space, and the remains of the only two Buran vehicles are actually rusting away today in a warehouse in Kazakhstan. Here’s an amazing picture of the abandoned Buran at the Baikonur Cosmodrome. Read more about that here.

But in Season 2, they’re up in the air.

I can’t wait.

“business cards”? what are you talking about?

Kids, back in the day, you used to “travel” sometimes and “meet people” “in person” and, amazingly, you might “hand” them one of these things.

I should really find a nice frame for all of these.

cableshare, 1981

Cableshare! 1981! My first job after graduating. Long enough ago that your card didn’t show an email address, which is strange because one of Cableshare’s products was an enterprise email system. But, dig the Telex number. I don’t think I ever got a Telex. But at Cableshare, I was lucky to work on a touch-screen network information system for shopping malls using Telidon, which I really need to write up at length. That was pretty cool. Absurdly expensive, and the touch screens were REALLY flaky, but hey, I was working on touch screen systems in 1982, and I still am today. Today’s touch screens are better.

grad school at Waterloo, 1983

back in my grad student days someone figured out how to order UW Business Cards. I remember this coming in handy exactly once, when trying to rent a townhouse and persuade the landlord that no, I wasn’t a student, I was obviously a RESEARCHER.

I think the UUCP email address certifies me as old-school. also “ihnp4” means “Indian Hills Network Processor 4.”

the Warriors Band, 1984

I snuck in another order, as leader of the University of Waterloo Warriors Band. Check this out, the band had an email address! watmath!watbun!war.band. This email was set up in about 1980, which could mean that the Warriors Band was one of the first bands in the entire world to be emailable. Maybe.

Math Faculty Computing Facility, 1985

What’s the easiest thing you can do when you’re done being a grad student? Slide into an IT job with the Math faculty. First card with a proper domain name address on it, but you can see UUCP emails are hanging on for dear life. Also my first experience with a manager with a pretty relaxed attitude towards whatever your job title on the card was – thank you, Bill Ince. I’ve always thought of myself as A Software Kind of Guy.

Indiana, 1988

Grad school friend Greg Rawlins somehow recruited me to come work for Indiana University for a couple of years. UUCP email addresses seem to have disappeared, but that was an amazing experience in an exotic foreign land, where I wound up buying a NeXT cube because I wanted a cheap ($11,000, WITH the academic discount) Unix computer at home. That led to …

NeXT, 1991

This is the position off from which I was laid in 1993.

That email address steve_hayman@next.com was a little clunky, and NeXT let you choose an additional alias, and for a brief period of time I was steve@next.com, a tremendously bad idea, but that’s worth of another story. Regret I did not hang on to that email address long enough to get a business card out of it.

More to come.

Thirty years ago today I achieved my first mild dose of Internet fame, with this post to the old comp.sys.next Usenet newsgroup. Here’s the original post first – and let me tell you about what happened afterwards. Also it involves ducks.

Date: Sun 23-Jan-1991 21:15:24 
From: sahayman@iuvax.cs.indiana.edu (Steve Hayman)
Subject: NeXT "audio ping" for network debugging

The thinwire started messing up in the building where I work yesterday;  I was scurrying around with an ethernet terminator cutting off segments of the network to try to isolate where the problem was.   I have a NeXT and a Sun on my desk, and was trying to 'ping' the Sun from the NeXT.  Whether it worked depended on where I cut the network off.

ping is a good tool for debugging but it sure is a pain to have to run back to your office to see if any of the ping packets are getting through.  So I came up with this quick hack.

1) Use "sndrecord ping.snd", hit return, say the word "PING" into the mike  hit return again.  Try to make the recording less than 1 second long.

2) Run this script

#!/bin/sh
# audio-ping host
# output of 'ping' looks like this:
#    # ping porbeagle
#    PING porbeagle.cs.indiana.edu: 56 data bytes
#    64 bytes from 129.79.254.138: icmp_seq=0. time=3. ms
#    64 bytes from 129.79.254.138: icmp_seq=1. time=3. ms
#          ...
# one line per second.  no output is produced if the packets
# aren't coming back.  
# This script plays a sound whenever it sees a line with "icmp_seq" on it.
#


ping $1 2>&1 | while read line; do
    case "$line" in
    *icmp_seq*) 
        sndplay ping.snd
        ;;
    esac
done


Now start this up.  Crank up the volume on your NeXT to the max.  You can now wander through the building fiddling with the network, unplugging different machines and so on; if it's working you'll hear this voice saying PING ... PING ... PING; if it quits working the voice will stop.

If you wanted to get really fancy you could play a different sound for some of the other messages that ping might generate - sometimes ping says "network is down", for instance.

This script helped me find a faulty tee-connector in just about a minute.

OK it's a dumb hack.

Steve

ping? what’s that?

ping is a Unix tool that attempts to make a connection to a remote computer, and once a second, it will print a line of received data. It’s a quick way to check if your network is working. Ping a faraway computer, and if you get a line of information back every second, your network is working.

I still use this today.

so what where you trying to do in 1991?

I was working for the computer science department at Indiana University – we’d temporarily been relocated to, I think, this building –
while the main CS building was being renovated (and wow, did I ever wind up with a great office in the renovated building when it was done, Lindley Hall – corner office, top floor, overlooking the quad… and two weeks after we moved in, I quit to come back to Canada. I’ll never have an office like that again.)

Anyway.
The network in our little house wasn’t working. I was running this ‘ping’ program and had to keep returning to my desk to see if it was working, as I experimented with changing network settings and futzing with cables on other computers in the building. We didn’t have portable computers, that’s for sure.

So what I did above was to combine the sound recording tool on my NeXT cube on my desk, with the Unix ping program, in a way that my computer would play a recording of me saying PING once a second when the network was working, and it’d be silent otherwise. I could then wander through the building adjusting things and when I heard the PING sound from upstairs, I knew I’d fixed it.

I didn’t think this was such a big deal but posted the above writeup to the net.
A few people congratulated me.

and then what?

Somehow this little hack made it into the Jargon File, a legendary compilation of hacker terminology, and a subsequent book, The New Hacker’s Dictionary.. If you check the jargon file today, 30 years later, you can see this entry for ping–

ping [from the submariners’ term for a sonar pulse] 1. n. Slang term for a small network message (ICMP ECHO) sent by a computer to check for the presence and alertness of another. The Unix command `ping(8)’ can be used to do this manually (note that `ping(8)”s author denies the widespread folk etymology that the name was ever intended as acronym `Packet INternet Groper’). Occasionally used as a phone greeting. See ACK, also ENQ. 2. /vt./ To verify the presence of. 3. /vt./ To get the attention of. 4. /vt./ To send a message to all members of a mailing list requesting an ACK (in order to verify that everybody’s addresses are reachable). “We haven’t heard much of anything from Geoff, but he did respond with an ACK both times I pinged jargon-friends.” 5. /n./ A quantum packet of happiness. People who are very happy tend to exude pings; furthermore, one can intentionally create pings and aim them at a needy party (e.g., a depressed person). This sense of ping may appear as an exclamation; “Ping!” (I’m happy; I am emitting a quantum of happiness; I have been struck by a quantum of happiness). The form “pingfulness”, which is used to describe people who exude pings, also occurs. (In the standard abuse of language, “pingfulness” can also be used as an exclamation, in which case it’s a much stronger exclamation than just “ping”!). Oppose blargh.

The funniest use of `ping’ to date was described in January 1991 by Steve Hayman on the Usenet group comp.sys.next. He was trying to isolate a faulty cable segment on a TCP/IP Ethernet hooked up to a NeXT machine, and got tired of having to run back to his console after each cabling tweak to see if the ping packets were getting through. So he used the sound-recording feature on the NeXT, then wrote a script that repeatedly invoked `ping(8)’, listened for an echo, and played back the recording on each returned packet. Result? A program that caused the machine to repeat, over and over, “Ping … ping … ping …” as long as the network was up. He turned the volume to maximum, ferreted through the building with one ear cocked, and found a faulty tee connector in no time.

I gotta tell ya, to have your name mentioned in the Jargon File certainly gives you an aura of street cred in certain strange circles!

not only that

The Ping program itself was written by a legendary Unix developer at AT&T Bell Labs named Mike Muuss. He tragically passed away in a car accident in 2000 but his personal web site lives on, and I was delighted to see his page titled, The Story of the Ping Program.

He tells the interesting story of the birth of this program and then – much to my delight – includes this anecdote, which is mostly accurate

The best ping story I’ve ever heard was told to me at a USENIX conference, where a network administrator with an intermittent Ethernet had linked the ping program to his vocoder program, in essence writing:

ping goodhost | sed -e 's/.*/ping/' | vocoder

He wired the vocoder’s output into his office stereo and turned up the volume as loud as he could stand. The computer sat there shouting “Ping, ping, ping…” once a second, and he wandered through the building wiggling Ethernet connectors until the sound stopped. And that’s how he found the intermittent failure.

Imagine my delight at stumbling across that, from the author of ping himself.

the best part

There’s a famous children’s book from 1933 called “The Story about Ping”. It’s about a duck, of course. A Duck! Ping, a spirited little duck who lives on a boat on the Yangtze River and gets into various misadventures. It’s about a duck. A duck named Ping.

But Mike Muuss’s page mentioned this legendary Amazon review of the book which still makes me laugh today.

Customer Comments

A reader from Upper Volta, Uzbekistan, March 7, 1999

Excellent, heart-warming tale of exploration and discovery. Using deft allegory, the authors have provided an insightful and intuitive explanation of one of Unix’s most venerable networking utilities. Even more stunning is that they were clearly working with a very early beta of the program, as their book first appeared in 1933, years (decades!) before the operating system and network infrastructure were finalized.

The book describes networking in terms even a child could understand, choosing to anthropomorphize the underlying packet structure. The ping packet is described as a duck, who, with other packets (more ducks), spends a certain period of time on the host machine (the wise-eyed boat). At the same time each day (I suspect this is scheduled under cron), the little packets (ducks) exit the host (boat) by way of a bridge (a bridge). From the bridge, the packets travel onto the internet (here embodied by the Yangtze River).

The title character — er, packet, is called Ping. Ping meanders around the river before being received by another host (another boat). He spends a brief time on the other boat, but eventually returns to his original host machine (the wise-eyed boat) somewhat the worse for wear.

The book avoids many of the cliches one might expect. For example, with a story set on a river, the authors might have sunk to using that tired old plot device: the flood ping. The authors deftly avoid this.

Who Should Buy This Book

If you need a good, high-level overview of the ping utility, this is the book. I can’t recommend it for most managers, as the technical aspects may be too overwhelming and the basic concepts too daunting.

Problems With This Book

As good as it is, The Story About Ping is not without its faults. There is no index, and though the ping(8) man pages cover the command line options well enough, some review of them seems to be in order. Likewise, in a book solely about Ping, I would have expected a more detailed overview of the ICMP packet structure.

But even with these problems, The Story About Ping has earned a place on my bookshelf, right between Stevens’ Advanced Programming in the Unix Environment, and my dog-eared copy of Dante’s seminal work on MS Windows, Inferno. Who can read that passage on the Windows API (“Obscure, profound it was, and nebulous, So that by fixing on its depths my sight — Nothing whatever I discerned therein.”), without shaking their head with deep understanding. But I digress.

here, for the record, is how what will probably be a future family running gag was born. A completely true story of the events of the evening of December 25, 2020.

The Christmas Potato Masher

A new fable for our times.

Christmas was quiet. Just me and my spouse.
All four of our children moved out of the house.
Mama in her kerchief and I in my cap
Had just settled down for an empty-nest nap.

When what to our wondering ears should appear,
But a phone call from Tyler. “Help me, Mama dear!
We’re cooking our dinner. Can you be here in a flash? er…
It turns out we don’t have a potato masher.”

As dry leaves before the wild hurricane fly,
When your son needs some help, you must leap to the sky!
We found our lone masher, and got into the car
And drove to see Tyler. (It wasn’t too far.).

We handed it over – a small ceremony
Took place. See the photographic testimony
But as we drove off, across the street, saw a store
Rabba Fine Foods. Open 7/24!

We thought they might have a small utensil section
Perhaps a new masher’d be in their selection
And lo! They had one potato masher there
For $4.99. ‘Twas the last one, I swear

“Thank you for this Christmas miracle”, I said
To the clerk, and he smiled and nodded his head
“That’s why we’re all here”, he declared, as I paid
And we drove back to Tyler, to offer a trade.

“Give us back the old one”, we asked, “Make it quick.
It’s plastic, and all of OUR pans are non-stick.
I’ll trade you this new one from Rabba. It’s metal.
We’ll take one more picture, and that will be settled.”

A new running gag was created that night,
The mashers might now be an annual sight.
Get ready for photos on Facebook each year
More potato mashers will surely appear!

Blogging this for posterity. Anybody who’s ever played in a band or orchestra has probably done the Leroy Anderson classic Sleigh Ride a bunch of times – and if you have, I hope you’ll enjoy this incredible version.

Is this brilliant or terrible or both? It takes a lot of skill to produce a train wreck like this. I find something new to laugh about every time. The pianist arbitrarily changing keys, the other players rushing to catch up, the ending that goes on too long, the final guitar honk, and maybe my favourite bit – all the extra eighth notes the second time through the bridge at 1:02 or so.

It reminds me a bit of Argonotes. Talented musicians all acting as directionless independent contractors and nobody really following the leader too carefully, and everybody having fun.

The Youtube comments give us an explanation.

This was recorded in one take by Nashville studio musicians in 2007, during a recording session for a legitimate artist’s Christmas project. The artist intended to use this as a “hidden track”, but then decided their audience wouldn’t get the joke.

Well that would be me, Jerry McPherson, on guitar, Scott Williamson on drums, I believe it was Joeie Canaday on bass, and the always amazing Jason Webb on piano.

This is a new Christmas favourite for me.