The Episode Is Already There

When a guest booked a recording with me, here's what happened next: nothing, until I did something about it.

Their booking sat there. Later, I'd open PodGlue, find the booking, and click a button that said "Create Part 1 Episode." That would take everything they'd typed into the intake form, their bio, what they wanted to talk about, their links, and turn it into an actual episode I could prepare against.

It's one click. I've done it hundreds of times. And that's exactly why I stopped seeing it as work.

Now the episode is already there. A guest books, and by the time you look, their episode exists, populated from what they told you, with the guest linked to it.

The technical shape of this is more interesting than it sounds, and it's the reason it took a bit of thought rather than an afternoon.

The obvious approach is: when a booking gets created, also create the episode. The problem is there are four different ways a booking can come into PodGlue, through the app, through the public booking page on the website, imported from your calendar, or confirmed manually by you. Wiring "and also create the episode" into all four means all four have to remember. And the one you forget is the one that breaks quietly, six weeks later, for the surface you use least.

So instead of doing it at the moment a booking is made, PodGlue now just periodically asks a question: is there a confirmed booking here that doesn't have an episode yet? If yes, make one.

That question can't be wrong. It doesn't care which door the booking came through. Ask it twice and nothing bad happens, because the second time the answer is already no. Miss a run and the next one catches it. It's a much duller design than hooking into the booking flow, and duller is what you want for something that runs unattended.

One thing I decided against, deliberately. When you click the button by hand, PodGlue also generates the episode blueprint, the run of show, the questions to ask. The automatic version doesn't do that yet. It's a genuinely different piece of machinery, and rushing it in would have meant copying a lot of logic into a second place where it could quietly drift out of sync with the first. So for now the episode arrives ready and the blueprint is still a click away.

I mention it because it's the honest version. The automatic episode isn't quite identical to the one you'd have made yourself, and you'd have noticed eventually and wondered why it looked thin.

There's also a bit of housekeeping that came out of this that I found funny in a bleak way. While building it I went looking for a piece of logic I needed on the server, and found a comment in the code saying "the server mirrors this, keep both in sync." It didn't say where the mirror was. I eventually found it buried inside an unrelated function, doing its own thing, untested, agreeing with the original purely by luck.

Both copies are now one copy, with a test that fails if anyone changes one without the other. Which is the sort of thing nobody will ever notice working, and would definitely have noticed breaking.