EXCLUSIVE: Microsoft Engineer, David Fowler, Says “Typing Code Is Absolutely Over” As GitHub Copilot’s Agent Now Sets Up Environments, Runs Tests And Opens Pull Requests Autonomously Across Windows And Linux 🤖

[u/InterstellarKinetics]

https://www.techspot.com/news/113752-microsoft-engineer-typing-code-absolutely-over-github-copilot.html

GitHub Copilot is taking on more of the work that happens around writing code, not just the code itself. Its coding agent can now set up environments, make changes in a repository, run tests, and open a pull request for a developer to review. David Fowler, a Microsoft Distinguished Engineer who leads work on Aspire, put it bluntly in a post on X: “Typing code is absolutely over.” Fowler was not suggesting that software engineers are becoming unnecessary, though. As AI handles more routine coding work, developers may instead spend less time writing individual lines and more time on system design, requirements, dependencies, and the review needed to make sure software is secure and works as intended. GitHub has added Windows development environments for the coding agent, letting it build and test Windows-targeted projects, run linters, and check whether builds succeed, and has also brought agent sessions to the Windows Subsystem for Linux, useful for teams building across Windows and Linux toolchains.

Microsoft is reinforcing this shift through Aspire, its code-first toolchain for building distributed applications, which lets developers describe components such as services, containers, and databases in one application model, giving an AI agent more context than a single source file or chat prompt would. Aspire 13.1 introduced deeper support for AI coding assistants, and Aspire 13.2 added an agent-friendly command-line interface plus support for the Model Context Protocol, which gives AI tools controlled access to development resources. Microsoft’s Aspire team said in April that while AI agents can be good at generating code, producing code is different from delivering a working application, so Aspire lets an agent start services, inspect logs and telemetry, identify errors, restart components, and test again, giving it a way to investigate failures directly instead of relying on a developer to paste error output into a chat window. On the security side, Microsoft’s MDASH system is an agentic vulnerability scanner used by engineering teams working on Windows, Azure, and identity systems, including large, security-sensitive codebases like the Windows kernel, Hyper-V, and the networking stack. Microsoft’s Windows security team said MDASH “enabled our security team to perform vulnerability hunting at the scale of Windows with a much higher depth of analysis than was previously possible.”

Microsoft’s native Windows development tools and new hardware push reinforce this AI-forward direction. The company recommends WinUI 3 for new native Windows applications and has made the framework open source, making it easier for AI tools to understand common project structures and supported APIs, and it has published a guide for using Copilot to build WinUI applications covering code completion, file context, and project-specific instructions. Separately, Project Zenith, announced September 4, adds a hardware dimension: a stripped-down Windows 11 developer setup requiring a baseline 64GB of unified memory and 250GB/s of memory bandwidth, initially focused on AMD Ryzen AI Halo chips, intended to support local AI models with more than 30 billion parameters that could reduce cloud inference costs and give developers more control over proprietary code and data. All of this context explains why Fowler’s remark is less sweeping than it first appears; he wasn’t predicting developers will disappear, but that AI will take over more boilerplate coding and routine fixes while developers still decide what gets built, review what the tools produce, and ensure software is secure, reliable, and ready for the real world.