Microsoft engineer wrote no code three months

Aral Balkan’s May 23 Mastodon post offered a compact anecdote about how AI coding tools are changing software work inside large companies. Balkan wrote that he had spoken “today at a social event” to a Microsoft software engineer working on Copilot Studio, and that the engineer said he had not written “a single line of code in over three months.” (mstdn.io) Balkan added that the engineer was “ashamed,” a detail that made the post travel beyond a routine product observation and into the question of what counts as engineering work when AI systems handle more of the implementation. (learn.microsoft.com) The claim is a single social-media account and not an official Microsoft statement, but it aligns with how Microsoft describes Copilot Studio itself: a platform for creating agents, topics and workflows through natural-language instructions and orchestration tools. ### What exactly did Balkan say the engineer told him? Aral Balkan wrote that the Microsoft engineer worked on Copilot Studio and had spent more than three months without directly writing code. (mstdn.io) The post said the engineer had instead been creating plans in natural language for AI systems to carry out. The wording matters because Balkan did not describe the engineer as idle or detached from building software. He described a shift in the form of the work: from typing code to specifying intent, reviewing outputs and directing systems that generate or assemble the implementation. (mstdn.io) That distinction comes from Balkan’s account, not from Microsoft. ### Why does Copilot Studio make that anecdote plausible? Microsoft’s Copilot Studio documentation says users can “build an agent flow with natural language,” “create and use prompts,” and generate topic structures from human-written descriptions. (mstdn.io) The company’s FAQ says the system is designed to generate an agent topic from a written description and produce connected nodes that achieve that goal. Microsoft’s training materials also say Copilot Studio can be used to create agents “without the need to write any line of code.” That language is aimed at customers and builders using the platform, but it helps explain how an engineer working on or around such a product could spend long stretches specifying behavior in plain language rather than writing code directly. (mstdn.io) ### Does this mean the engineer stopped doing engineering? The May 23 post does not say that. Balkan’s account describes a change in interface, not an end to technical work. (learn.microsoft.com) Microsoft’s implementation guidance for Copilot Studio lists project leads, solution architects, technical leads and administrators among the people involved in building and managing agents. The company’s materials describe planning, evaluation, governance, analytics and iterative refinement as part of the workflow, suggesting that instruction-writing, review and system design can sit alongside traditional coding. (microsoft.github.io) ### What can actually be verified here? The verifiable core is narrow. (mstdn.io) Aral Balkan posted on May 23 that he had spoken to a Microsoft engineer on Copilot Studio, and Microsoft publicly documents Copilot Studio as a platform that lets people create agent behavior through natural-language descriptions and low-code or no-code tools. The engineer’s identity, the exact scope of his role and whether “no code” meant no hand-written production code, no local code edits or no coding at all have not been independently confirmed in the sources reviewed here. (learn.microsoft.com) Microsoft’s public documentation remains the clearest next place to watch because it is where the company is documenting how Copilot Studio handles prompts, workflows, tools and code execution. (learn.microsoft.com) (mstdn.io)