A daily briefing for a software engineer
A recurring show scoped to your stack rather than to technology in general, and the upload that turns a week of your own changelogs into a catch-up.
The short answer
Describe a recurring show naming the languages, frameworks and infrastructure you actually run, and ask for breaking changes, security advisories and migrations first. Scoped that way it is five minutes; described as ‘software engineering news’ it is an unlistenable survey.
How to set it up
List the stack by name
Postgres 17, Next.js, whatever your runtime and cloud are. The whole value here is scope: a show that names five things covers them properly, and a show about ‘backend development’ covers nothing.
Put advisories and breaking changes first
‘Lead with anything that would break a build or require a patch, then interesting things after’ gets the useful part into the first ninety seconds, which is as far as a morning show reliably gets listened to.
Upload your own week for the other half
Export a week of merged pull requests or release notes, upload them, and ask what changed and what is now inconsistent. This is the catch-up nobody has time to write, and it is specific to your codebase in a way no researched show can be.
At a glance
- Suggested cadence
- Weekday mornings
- Suggested length
- 5–8 minutes
- Key instruction
- Name the stack; lead with breaking changes
- Repository access
- None — you paste a link or upload an export
Hear what comes out
Shows already published on Lissin, free to play in the browser.
Questions
- Can it watch a repository?
- No. There is no source-control integration and nothing is watched. A public release-notes or changelog URL can be pasted in, and a private one exported and uploaded — either way you are the trigger.
- Is it a substitute for a security advisory feed?
- Absolutely not. Subscribe to the real advisories for anything you run in production. A briefing might mention one; a feed guarantees it.
- Will it read code?
- It reads code as text, which is not useful aloud. Ask for what a change does rather than for the diff.
What this does not do
No repository, CI or issue-tracker access. A generated show is a poor primary source for anything security-critical, and should sit behind the official channels rather than in front of them.
Try it on something you already have
Upload a PDF, a deck or a document and describe the show you want from it. Or press play on anything in the library first — no account, no app.
Last reviewed 9 September 2026 by Lissin Editorial.