← All speakers

Bio, Work & Ideas

John Peck

Conference affiliation: GitHub · 2025

John Peck, known professionally as Jon Peck, is senior product marketing manager at Evinced, where he focuses on digital accessibility and AI-assisted software development. Previously, he helped establish GitHub’s Enterprise Advocacy team in the Americas, guiding organizations through developer collaboration, security, and the adoption of coding assistants.

His earlier career included work with Cornell University, Massachusetts General Hospital, startups, consulting, and Algorithmia, where he worked on serverless machine-learning services and production deployment. He also developed hands-on training for deploying machine-learning models as microservices.

After joining GitHub in 2020, Peck worked in its Executive Briefing Center before moving into technical advocacy and enterprise developer relations. His guide to collaboration-ready repositories emphasized documented ownership, contribution rules, and project purpose—principles that later shaped his approach to giving coding agents usable context.

At AI Engineer World’s Fair 2025, he assisted Christopher Harrison with a hands-on GitHub Copilot workshop, helping participants configure accounts and repositories. Peck’s distinctive contribution was that technical leads should record architectural decisions, dependency choices, and coding patterns in shared instructions as teams make them.

His projects include Copilot Chat to Markdown, which converts coding-assistant conversations into reusable documentation.

Read the topics behind these talks

1 conference talk

Key ideas

Scroll to read ↓

From a changing brunch request to a reviewable pull request, effective Copilot collaboration depends on explicit context, prepared environments, and deliberate human control.

  • First brunch, then somewhere new, then waffles
    3:51 ↗
  • Choose how much of the work to delegate
    8:32 ↗
  • Get the lab into a working environment
    11:09 ↗
  • Give the issue requirements and the agent an environment
    30:35 ↗
  • Continue the work through the pull request
    36:11 ↗
  • Put durable context in the repository
    42:07 ↗
  • Apply repeatable patterns to the right files
    45:09 ↗
  • Keep the review process and take over when useful
    51:03 ↗
  • Remote MCP access carries credentials and authority
    56:16 ↗
  • Separate issue environments, compose shared guidance
    58:31 ↗

References