You think this podcast description stuff is easy, don't you? I've said this before, but I'm employed as a podcast description writer. I have a PhD in technical writing and here I am, writing podcast descriptions. This is the only show the hosts forgot to tell me what I should be writing for podcast descriptions, so I use this description space to vent. This shit isn't easy, podcasting descriptions. You're probably wondering how I got into this game, right? Well, back in 1990 I was commissioned by Sanyo to write the translation of the owners manual and warranty card for the TAS 3450 Sanyo Answering Machine, which was known as having one of the most detailed, yet elegant owners manuals in all of electronic goods. I'm not talking elegant like, Carol Alt, Kim Bassinger, or even Princess Diana, I'm talking elegant in the technical sense: achieving maximum clarity and impact with minimal complexity. My work on the TAS 3450 really caught everyone's attention in the industry, and I went on to have a very successful technical writing career. Fast forward to 2026 and I'm writing descriptions for America's Last Newsroom, and NYTimes The Daily, and many many more. The difference between America's Last Newsroom and The Daily is unbelievable. Every time I've submitted a podcast description to The Daily, which is every day, they send back copious amounts of notes and changes that need to be made. America's Last Newsroom has never once read what I have written and approve it within seconds, making me think it's some sort of automated system they have (i'd love to know, maybe I could write a manual about that system). Never once have they opened an email, read my work, or even given positive feedback. So here we are, I get to use their show description as a diary, and you get to understand how technical writers are now writing podcast descriptions. I know no one reads this. Even you, why are you still reading? There's no information in here about the podcast ...