Urgent.News

What's breaking now, across thousands of outlets.

Tech

Turn a Live Q&A Transcript Into a Lesson and Recap With Python

If you run a community, a course, or even a team office hour, you probably record live Q&A sessions. Then the recording sits there. Nobody rewatches an hour of video. The fix is to repurpose each call into smaller pieces: a lesson built from the best answer, a short recap, and a list of questions you didn't get to. Here's a small Python script that does the boring part for you. The input Most…

If you run an online community, course, or team office hours, you likely record live question and answer sessions. However, those recordings often go unused as nobody rewatches an hour of video. The solution is to repurpose each call into smaller, more digestible pieces: a lesson built from the best answer, a short recap, and a list of unanswered questions for the next meeting. A small Python script can automate this process for you.

Most meeting and recording tools can export a transcript in plain text format. We'll assume a text file where questions start with "Q:" and answers start with "A:". If your tool's format is different, a simple find-and-replace should suffice. In the transcript, example questions include "How do I automate lead follow-up?" and "Should I use Zapier or write code?". Notice that the last question, "What about CRMs?", has no answer, which could represent next month's agenda.

The script starts by importing necessary modules, including regular expressions and the Path class for file handling. The parse_transcript function splits the input text at each "Q:" line, creating pairs of questions and answers. It then uses regular expressions to extract the question and answer from each block. If there's no answer, the answer is set to an empty string.

The build_outputs function sorts these pairs into two lists: answered and unanswered. It identifies the longest answer as the best answer, which is likely to be a detailed explanation, making it a good candidate for a lesson. You can modify this rule to use chat reactions, a manual selection, or an LLM scoring each answer.

The script then writes three files: lesson.md, recap.txt, and agenda.txt. The lesson.md file can be pasted into your course section, recap.txt provides five bullets for a discussion post, and agenda.txt lists the unanswered questions for the next meeting. In the future, you could automate pulling transcripts directly from your recording tool's export folder, running the script on a schedule, and sending the recap to a webhook that posts it to your community or Slack.

Adding a summarization step could also enhance the recaps, providing a one-line answer to each bullet instead of just repeating the question. The goal isn't the complexity of the code, but the ability to transform one live hour into a week of valuable content without manually rewriting it.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Nothing dead — giving every experiment a decision date

A system that only adds will eventually be mostly additions. That sounds obvious and is easy to forget in practice. An optional tool gets merged "for now"; a pilot document stays a pilot; a flag…

  • "Nothing dead" rule prevents accumulation of unused experiments
  • Every experiment, flag, tool, document, and code path must go ahead or be retired by a decision date
  • Systematic registry tracks experiments, owners, start and decision dates, and consumer status

The Cheaper HMI Is Costing You More: A TCO Breakdown for Engineers

Every procurement cycle hits the same wall. The membrane switch assembly quotes at a fraction of the panel PC price. The spreadsheet says “option A.” The line engineer says “option B.” Someone in…

  • Membrane switches suffer from drift-induced quality loss over time.
  • Membrane switch panels risk obsolescence with limited supplier alternatives.
  • Panel PCs reduce changeover time by up to 67% compared to membrane switches.

GDPR Article 22's "right to an explanation" is an engineering requirement in disguise

Every time Article 22 comes up, the same argument starts. Lawyers debate what "meaningful information about the logic involved" is supposed to mean, and engineers start reaching for SHAP plots.

  • Article 22 requires explanation of automated decisions
  • Finding specific decision and inputs is challenging
  • Auditability and organization are core compliance issues

How I Built a Real-Time Vehicle Inspection Lookup Tool for Colombia (2026)

A few months ago, a friend asked me how to check if his car had passed its mandatory technical inspection. I told him to go to the RUNT portal — but the experience was slow, confusing, and nearly…

  • Mandatory RTM inspection required for all Colombian vehicles.
  • Government data stored in RUNT database, but querying is problematic.
  • Lightweight lookup tool prevents costly fines and operational disruptions.

PyPI Package Hijack Without Repo Changes Exposes Source, Build, and Registry Trust Gaps

The Phantom Commit: How a Trusted Package Turned Hostile Without Touching GitHub When teams look at an incident like the Microsoft Agent Framework package compromise on PyPI, the first instinct is to…

  • PyPI package compromised without repo changes
  • Versions 1.26.1 and 1.26.2 contained credential-stealing code
  • Decoupling allows malicious wheels to bypass verification

More from Friday 20 November →