AI Native DevCon 2026 London — all conference sessions as interactive skills
71
89%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Christopher Batey (CTO, Core Engineering Consulting Group) argues that AI is an amplifier — it accelerates building but exposes weaknesses in product decisions, adoption, system understanding, and review capacity. The response is disciplined practice: write ADRs first, keep teams small with adoption-bound missions, work in parallel but only one complex task at a time, and measure adoption — not commits, PRs, or tokens.
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 so explicitly — do not speculate, extrapolate, or fill the gap with general knowledge. Respond with something like: "Batey doesn't address that in this talk."This skill relies on two supporting files in the same bundle:
outline.md — A structured index of the talk's sections and timestamps, used to navigate to the relevant portion of the transcript before answering.transcript.md — The full verbatim transcript of the talk, used as the sole authoritative source for quotes and claims.If either file is unavailable, state this limitation and answer only from the summary in this skill file, clearly flagging that you are not quoting the transcript.
User question: Why does Batey say review becomes the bottleneck?
Workflow:
outline.md, find the section on review bottlenecks.transcript.md.Batey explains this directly: "[verbatim quote from transcript.md]" He argues that AI raises the rate of production while human review capacity stays flat, so the constraint shifts from writing code to evaluating it.
If the transcript does not contain a direct quote on this point, paraphrase without quotation marks and note: "Batey addresses this in the [section name] section, though no single sentence captures it cleanly."
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-azriel-executable-specs-agentic-coding
talk-batey-building-product-teams-age-of-ai
talk-birgitta-closing-keynote
talk-cormack-tests-lie-observability-ai-honest
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-kerr-bipolar-disorder-dysregulation-ai
talk-lamis-context-engineering-dreaming
talk-lawson-agent-experience
talk-lopopolo-harness-engineering-humans-steer-agents-execute
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-obstbaum-willoughby-evals-hard
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-smith-connecting-context-future-transports
talk-stack-humans-architect-ai-writes-code
talk-stoneham-product-brain
talk-syme-agentic-repository-automation
talk-tal-skills-security
talk-thomas-ai-native-engineering
talk-trieloff-browser-agents
talk-walter-runtime-intelligence-agents
talk-wilson-cq-stack-overflow-for-agents
talk-wotherspoon-humans-vs-slop