← All speakers

Bio, Work & Ideas

Dave Burnison

Conference affiliation: GitHub · 2024

Dave Burnison is a senior enterprise advocate at GitHub specializing in how large organizations integrate GitHub Copilot into software development without discarding existing infrastructure. His work spans coding assistants, Azure DevOps, application security, enterprise governance, and the practical handoffs between planning, engineering, and deployment.

Earlier in his career, Burnison led release-management and database work at LexisNexis InterAction, coordinating a shared codebase across concurrent projects and distributed teams. He subsequently worked in DevOps consulting and technical sales before joining Microsoft in January 2016. That background informs his focus on adapting new development tools to established enterprise workflows.

By 2023, he was helping organizations apply GitHub Enterprise and Copilot across development, testing, and deployment. His AI Engineer World’s Fair 2024 demonstration traced Copilot’s expansion from code completion into repository-aware assistance, enterprise documentation, deployment integrations, and pull-request summaries. At Microsoft Build 2026, Burnison and Dan Hellem explored connecting Azure DevOps and GitHub throughout the software lifecycle.

  • Human review remains indispensable. When Copilot generated a Django relationship permitting unintended deletion of speakers and talks, Burnison showed why developers must identify flawed behavior, refine their instructions, and validate the result.
  • Repository context makes assistance actionable. An indexed enterprise application enabled Copilot to locate hard-coded sales-tax logic and its callers, suggest an Avalara integration, and flag the need to keep API credentials out of source code. Burnison treats repository-grounded enterprise knowledge as essential to useful, secure assistance.
  • Enterprise AI needs operational guardrails. His August 2026 enterprise roundup connects enterprise AI governance with model policies, managed settings, usage controls, security, and code quality.

Read the topics behind these talks

2 conference talks

Key ideas

Scroll to read ↓

A Django deletion rule, undocumented validators, deployment status, and a sales-tax refactor show how Copilot’s usefulness depends on the context developers supply and the decisions they retain.

  • Getting help with code you did not write
    0:16 ↗
  • A generated model still needs a deletion policy
    3:17 ↗
  • Give the generator an observable requirement
    5:56 ↗
  • Explain, restructure, then test
    7:53 ↗
  • Ask whether the change reached production
    11:08 ↗
  • Make “here at GitHub” mean something
    14:18 ↗
  • Find the business assumption inside the repository
    17:57 ↗
  • Turn repository context into an integration proposal
    21:05 ↗
  • Describe the change, then examine its intent
    24:25 ↗
  • Start modernization with understanding
    27:30 ↗

Key ideas

Scroll to read ↓

A hands-on path through Copilot in VS Code, from supplying useful context and reviewing JavaScript suggestions to understanding model latency, extensions, and multistep development.

  • What does Copilot need to help you write code?
    0:30 ↗
  • From editor context to a suggestion
    3:07 ↗
  • Make the request—and its context—explicit
    7:21 ↗
  • Good names and concrete examples reduce ambiguity
    14:22 ↗
  • Prepare the workshop environment
    19:27 ↗
  • Find the right participant and open a JavaScript file
    29:33 ↗
  • Ghost text, inline edits, and conversation
    36:22 ↗
  • Accept only the part you want
    41:22 ↗
  • Generate a URL parser, then inspect the repair
    47:00 ↗
  • Explain code, reset context, and generate tests
    50:36 ↗
  • Model quality has to fit the interaction
    59:30 ↗
  • Extend chat without assuming full model replacement
    1:04:22 ↗
  • Updated knowledge and automatic delegation solve different problems
    1:07:24 ↗
  • From a reviewed suggestion to a reviewed plan
    1:13:33 ↗

References