GitHub Engineering

GitHub rewrote the Copilot agent runtime from TypeScript/Node.js to 800,000+ lines of Rust, with AI agents writing most of the code across 128 incremental pull requests shipped in place rather than via a big-bang cutover. Reported gains include large reductions in startup time, memory, and CPU, plus an embeddable C-ABI surface for six SDK languages, at the cost of ~$120K in tokens, explicit lifetime management, and some regressions. The author frames it as escaping Node/V8 overhead for embedded runtimes, not a general claim that TypeScript should become Rust.

A GitHub marketing lead automated event operations end-to-end by treating each event as a GitHub Issue: issue forms capture inputs, labels act as triggers, GitHub Actions stage the event, and Copilot 'skills' (Markdown runbooks) handle planning and post-event follow-up. She argues the pattern applies to any repetitive work touching tools with an API or CLI, weighing it against packaged marketing-automation platforms: regional variation favors custom pipelines with PR-based change management, though a silent cron failure shows monitoring is still required.

The article pushes back on five common AI hot takes: that you can skip reading AI-generated code, that not using AI hurts hiring, that Skills killed MCP, that RAG is dead, and that needing fine-tuning signals bad code. It argues each is oversimplified—review depth should match actual risk, AI fluency is about judgment, MCP and Skills solve different problems, and RAG still grounds answers. It closes by urging readers to test ideas by building rather than debating.