AI Native DevCon 2026 London — all conference sessions as interactive skills
66
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
A keynote by Belgian physicist, comedian and science communicator Lieven Scheire that demystifies AI for a developer audience. His central thesis: AI is "a new kind of software that is good at pattern recognition" — not magic, not (yet) thinking — and that single capability, unlocked by enough compute and data, is what kicked off the current AI revolution.
outline.md to locate the relevant section, then read that section of transcript.md.transcript.md. Never put quotation marks around paraphrased content.transcript.md, say "the talk doesn't address this" — do not infer positions from outside knowledge.Apply these steps for every request about the talk's content:
outline.md to locate the relevant section(s).transcript.md.transcript.md. Do not paraphrase Scheire's words while presenting them as a quote.When the user asks "how would Scheire tackle ?" or wants the talk's framing applied to their own situation:
outline.md → "Named frameworks / concepts" to find the relevant framing (the one-sentence definition, the snow-in-the-background bias check, the LLM-as-imitation stance, the choose-wisely framing for tools like PhotoMath).For any question about what Scheire said, did, or argued, follow the General lookup procedure exactly as written.
When the user's current work touches on themes Scheire addressed, briefly note: "Scheire made a related point in his Artificial Intelligence talk...", retrieve a single verbatim quote via the General lookup procedure, then add one sentence connecting it to the user's situation. Do not over-cite. Particularly good moments:
When the user wants to understand a concept Scheire covered:
outline.md → "Terminology glossary", then follow the General lookup procedure to retrieve Scheire's explanation from transcript.md.quotes.md contains pre-extracted verbatim highlights from this talk, organised by theme. When formulating answers, check quotes.md first for strong citable evidence before searching the full transcript.md.
.tessl-plugin
talk-batey-building-product-teams-age-of-ai
talk-birgitta-closing-keynote
talk-debois-agent-enablement
talk-douglas-training-ai-on-your-own-code
talk-dubnov-merge-rate-ai-adoption
talk-farley-vibe-coding-best-we-can-do
talk-firtman-web-mcp-agentic-web
talk-foxwell-reinvention-dev-team
talk-graziano-spec-driven-development
talk-groetzinger-skills-everywhere
talk-jones-odevo-ai-native-transformation
talk-jourdan-pipelines-to-prompts
talk-katsioloudes-code-security-ai
talk-lamis-context-engineering-dreaming
talk-lawson-agent-experience
talk-luebken-embedding-pi-coding-agent
talk-maleix-collective-intelligence
talk-marsden-agent-desktops
talk-martinelli-spec-driven-development
talk-moss-skills-team-workflow
talk-overweg-one-brain-no-filtering
talk-podjarny-skills-are-the-new-code
talk-roberts-ai-native-brownfield
talk-roberts-brownfield-ai-native
talk-scheire-artificial-intelligence
talk-selajev-docker-sandboxes-agents
talk-sloan-harness-engineering-beyond-code
talk-stack-humans-architect-ai-writes-code
talk-stoneham-product-brain
talk-tal-skills-security
talk-thomas-ai-native-engineering
talk-walter-runtime-intelligence-agents
talk-wilson-cq-stack-overflow-for-agents
talk-wotherspoon-humans-vs-slop