Thinking about a workflow like this for helping prevent comprehension debt on a fast-moving repo:
Fast-moving repo w/lots of changes
-> once per day/week, grab a diff of the changes
-> feed it to an LLM to output a podcast transcript, focusing on the 'why' of what changed more than the 'what
-> feed the podcast transcript to a TTS API
-> publish to a private podcast feed
-> listen on your commute/morning run/lunch break
I'm doing this for my personal wiki, which ingests from X/Slack/Discord/Gmail, and it's super-efficient for keeping me in the loop.
Post #81
79