← All speakers

Bio, Work & Ideas

David Smith

Conference affiliation: Microsoft · 2024

David Smith is a statistician, open-source community builder, and AI engineering advocate whose work spans the development of the R ecosystem and production-ready generative AI. He co-authored An Introduction to R, helped establish the R Consortium, and later taught developers to build and evaluate AI applications grounded in business data.

From R to applied AI

Smith studied statistics at the University of Adelaide and Lancaster University. His work with Bill Venables at Adelaide helped form the R Project’s official introductory manual, and he contributed to the early development of Emacs Speaks Statistics.

He directed product management for S-PLUS at Insightful before becoming chief community officer at Revolution Analytics, where he wrote extensively about R and data science for the Revolutions blog. In an essay on open-source data science, he argued that shared software, inexpensive infrastructure, and collaborative development made large-scale analytics economically viable.

After Microsoft acquired Revolution Analytics in 2015, Smith moved into Microsoft’s developer ecosystem. He helped launch the R Consortium that year and subsequently served on its board as treasurer. His later work at Microsoft and GitHub included leading AI and machine-learning advocacy and serving as a principal AI advocate. His personal GitHub projects include Copilot for R and prompt-engineering workshops. He has since announced his departure from Microsoft and GitHub; no subsequent employer is independently established.

  • Hybrid retrieval for production applications. Smith recommends combining keyword and vector search, arguing that the combination can retrieve relevant information more effectively than semantic similarity alone. His retail-copilot workshop, co-led with Cedric Vidal, combined product search with customer purchase histories to generate personalized answers.
  • Groundedness as an engineering requirement. Smith evaluates model responses for coherence, fluency, relevance, and factual grounding. His example of a chatbot inventing a nonexistent toothbrush shows why polished language cannot substitute for checking answers against actual source data. The Contoso Chat sample demonstrates the associated retrieval, deployment, and evaluation workflow.
  • Continuous evaluation and prompt-injection awareness. Smith treats production AI as a cycle of prompt refinement, retrieval tuning, adversarial testing, monitoring, and reevaluation as models or data change. He highlights prompt injection as a particular concern when user input influences generated database queries, alongside access controls and customer-data boundaries.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

Follow a retail RAG backend from product retrieval and customer lookup through prompt assembly, deployment and an evaluation that catches a convincingly invented product.

  • What information does a retail chatbot need?
    0:00 ↗
  • A tent recommendation, then a purchase-history question
    7:07 ↗
  • Two retrieval paths meet in one prompt
    10:55 ↗
  • Launch the lab, authenticate and inspect the data
    16:22 ↗
  • What a flow owns
    40:13 ↗
  • Prompt flow, application orchestration and the playground
    49:48 ↗
  • Connections, persistence and search quality
    1:04:31 ↗
  • Customer context is not customer authorization
    1:17:25 ↗
  • From lookup results to a rendered prompt
    1:26:51 ↗
  • Run locally, package the flow and understand its limits
    1:33:50 ↗
  • A fluent answer can still invent a product
    1:41:20 ↗
  • Use failures to change the system
    1:49:33 ↗
  • Uploaded PDFs need a retrieval lifetime
    1:52:02 ↗

References