Europe 2026
From Writing Code to Designing Systems: How the Developer Role is Changing — Chris Noring, Microsoft
Overview
The developer role is shifting from solely writing code to designing and managing complex systems, augmented by AI tools. This evolution means developers are becoming more efficient, acting as orchestrators rather than just coders. The core idea is to leverage AI to scale development efforts, enabling individuals to achieve significantly higher productivity while maintaining control through robust guardrails.
Who should watch
- AI engineers looking to enhance their productivity.
- Product Managers seeking to understand how AI impacts development workflows.
- Builders experimenting with agentic tools and system design.
- Developers feeling overwhelmed by the pace of AI advancements.
- Anyone interested in the future of software development and the changing role of engineers.
Key takeaways
- The primary entry point for development is shifting from editors to the command-line interface (CLI), allowing for quicker task management and issue resolution.
- AI tools, while powerful, require strict guardrails to prevent errors and ensure desired outcomes. Essential guardrails include `Agents.md` for high-level guidance and `skills` for repeatable, constrained actions.
- Custom agents offer a higher level of abstraction, enabling reasoning, planning, and orchestration of multiple skills to perform complex tasks with a defined persona.
- Developers can scale their output dramatically by delegating tasks to AI agents, transforming from 1x to potentially 20x or 100x developers.
- The editor remains a crucial "control board" for fine-tuning and oversight, even as the CLI and UIs become primary interaction points for AI-assisted development.
- AI agents can be seen as powerful tools, akin to switching from an axe to a chainsaw for cutting trees, drastically increasing efficiency.
- The human remains central in the loop, responsible for building the systems, setting instructions, and providing final approval before shipping.
- The shift is about augmenting, not replacing, engineers, preserving the need for the engineering brain in the industry.
Notable quotes
*My daytime job is at Microsoft where I work a lot with AI engineering.*
*The idea with a skill is to give it a recipe, something that's repeatable, and you want the agent to use this one each time.*
*We can scale in one of two different ways if you use Copilot, right? We can either scale directly from the CLI, or we can scale from the UI when we are looking at our GitHub repository.*
Unofficial community note. Prefer the recording for nuance.