
Don't Panic: The Lazy Speaker's Guide to CFP Triage
Every new CFP triggers the same ritual:
- Open the conference page
- Copy the dates
- Check for duplicates in GitHub
- Find the right labels
- Write the issue
- Add a comment with talk suggestions
β³ 42 minutes for 3 CFPs! But actually, 20 person-days per year across our team of 13 DevRels.
For. Copy-pasting.
My CFO nearly cried. π
So I looked around. Elastic already gave me Elasticsearch for semantic search, a native MCP server in Kibana, a conversational agent, a workflow engine and JINA Reader to parse the web. GitHub offered its own MCP server and GitHub Actions to handle updates.
In this session, I’ll show you β live, no slides β how I put all of this together to build an agent that does the work for us. One URL in β‘οΈ one complete GitHub issue out. With human validation, because I trust AI but not blindly. π
Whether you track CFPs or not, the patterns are here. Come for the lazy automation, stay for the architecture. So long, and thanks for all the fish. π