Failures of Raw Machine Transcripts
A personal anecdote describes the failure of pasting a raw, unformatted machine transcript onto a webpage, which resulted in a "long grey slab" that provided no value for two years. This highlights that AI assistants and human readers both require structured documents with headings and paragraphs rather than raw output.
machine transcription· user experience· formatting· timestamps· accessibility
07:07 But if they are, it's your guests saying what they said. You can't get more honest than that. Then let me take it the other way. If text is the whole game, the quality of the text matters. And I've watched podcasters dump a raw machine transcript under the player and call it done. I know someone who did that. We covered my transcripts in episode one. Thank you. I wasn't talking about you, actually. I did it too. Years ago, I pasted a machine transcript onto a page with no paragraphs, no headings, and timestamps that didn't do anything. One long grey slab. How long did it stay like that?
07:48 Two years, give or take. Mortifying. It did nothing, and I decided transcripts were a waste of time. It took me ages to work out that transcripts hadn't failed. That particular page had. Makes sense. Raw machine output is a wall of words. It gets most of them right, fair enough. But it doesn't know which bits matter, where one topic stops and the next starts, or what the episode's actually about. And an assistant deciding what to quote is far happier with something that looks like a document. Headings, sections, a clear sense of what each part covers. So what's the alternative? Paying someone to rewrite every transcript by hand? Not anymore.
