World's Fair 2024
Copilots Everywhere: Thomas Dohmke and Eugene Yan
Overview
This talk explores the evolution and integration of AI-powered coding assistants, focusing on GitHub Copilot. It posits that AI tools are shifting from simple autocompletion to comprehensive development partners, aiming to enhance developer productivity and democratize access to coding. The core thesis is that AI should augment human capabilities, not replace them, by handling tedious tasks and facilitating exploration within the codebase.
Who should watch
- AI Engineers
- Product Managers
- Software Developers (all levels)
- Builders looking to integrate AI into their workflows
- Those interested in the future of software development tooling
Key takeaways
- GitHub Copilot originated from early access to OpenAI's Codex model, with initial "aha" moments involving accurate syntax generation.
- The development of Copilot occurred entirely remotely during the 2020 lockdown, demonstrating the feasibility of innovation under distributed conditions.
- Internal testing showed exceptionally high Net Promoter Scores (NPS), indicating strong developer enthusiasm for the tool.
- Telemetry revealed that Copilot was responsible for a significant portion of code written, initially around 25% and growing to about half in some languages.
- The strategy for integrating AI across GitHub involves being highly agile due to the rapid pace of AI advancements and meeting developers where they are.
- GitHub's approach is human-centric, aiming to build AI *for* engineers rather than trying to create AI engineers, thereby improving developer experience.
- Tools like GitHub Copilot Workspace aim to bridge the gap between tasks (like GitHub issues) and code implementation, acting as a pair programmer for codebase exploration.
- AI assistants can democratize technology access by enabling coding in natural languages, benefiting non-native English speakers and those without technical backgrounds.
Notable quotes
*We're not trying to build an AI engineer we're trying to build AI for engineers a human Centric approach.*
*The human is still in the center; every step of that way you know writing a specification analyzing the current repo... the human can interact can change those bullet points can change the code.*
*An agent you know is like an AI dishwasher you fill it with you know the dishes and you let it do its thing and then at the end you to take the output and you put it back into to the shelves.*
Unofficial community note. Prefer the recording for nuance.