Loading…
Topic
GitHub Copilot
3 posts about GitHub Copilot. Every summary links to the original.
- 3 posts
- 2 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
Rendering huge pull requests in the GitHub Copilot app
Rendering a pull request with over a million changed lines and hundreds of threaded comments requires a fundamentally different architecture than a code-only diff. The standard virtualized approach fails because comment heights depend on render-time factors like markdown wrapping, expandable sections, and reply composers. The team split the document’s height into two independent domains: deterministic code geometry and dynamic block geometry for comments. A single idle- and scroll-gated measurement pass, scoped to the viewport, corrects heights without causing reflows mid-scroll. The result is a pull request view where a million-line diff with hundreds of comments opens, scrolls, and behaves like a normally sized pull request.
How we make AI coding more cost efficient without sacrificing task quality
GitHub Copilot’s AI coding efficiency work focuses on completed task cost rather than tokens in individual tool calls, because shorter responses can trigger recovery work. Using agentic coding benchmarks and controlled online experiments, the team evaluated selective output compression, removal of unused line-number prefixes, prompt shortening, and direct delivery of completed background results. The shipped compressor preserves source-like and arbitrary output, reorganizes search results without dropping content, and compresses repetitive install, build, test, and progress output while retaining a recovery path to originals. Removing line-number prefixes cut offline model-inference cost roughly 5% and online daily cost about 3%; direct background-result delivery reduced AI Credit usage about 2.3%, while prompt changes required workload-specific validation.
Cutting Through the Noise: Three Things We've Learned About Generative AI and Developer Productivity
eBay describes three tracks for generative AI developer productivity: adopting a commercial offering, fine-tuning an open-source LLM on internal data, and building a knowledge base. Because no single metric is reliable, the exercise combines surveys with Git, DORA, Flow, code-quality, and performance measures. In a 300-developer Copilot A/B test, the treatment group had 27% code acceptance, 17% faster pull-request creation-to-merge time, and 12% lower Lead Time for Change; Sonar quality was unchanged. eBayCoder, based on Code Llama 13B and trained on eBay code and documentation, is presented as useful for software upkeep and broader context. Its internal GPT uses retrieval-augmented generation to answer questions from distributed sources, but early results remain preliminary and nonsensical answers require feedback and RLHF.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.