Session: Scott and Mark learn... how agents reshape software engineering | BRK247
Microsoft Build 2026 featured an unusual breakout session: Mark and Scott — not next-gen engineers, but seasoned practitioners — showed live how they work with Claude on real technical challenges. What I saw, I recognized immediately.
The gap nobody talks about out loud
There is a significant leap from vibe-coded solo software to skilled engineering at world scale. AI makes it tempting to ignore that gap. You type a prompt, code rolls out, and it seems to work. But seems to work is not the same as works correctly under load, in production, across multiple teams.
Mark and Scott illustrated this honestly. What sets them apart is not speed or hype — it is deep domain knowledge, a sharp eye for when Claude goes wrong, and the discipline to stop and steer before things go off the rails.
What Mark managed to build
With careful guidance, Mark delivered two impressive things:
gRPC Shared Memory
When two gRPC processes run on the same machine, there is no reason to communicate over TCP or Unix sockets. Serialization across the network costs time and CPU. With shared memory, you can eliminate that overhead entirely.
Mark delivered a working implementation for both Go and .NET — two ecosystems, one concept, significant performance gains. This is not a hello-world demo. This is the kind of optimization that makes a difference in production systems.
In his spare time, Mark added a scrolling screenshot feature to ZoomIt, the well-known Sysinternals tool by Mark Russinovich. A small feature, but technically non-trivial — and a great example of what becomes possible when you use AI as a tool rather than a replacement.
The skill that deserves the most attention
The most interesting part of the session was not the code being written, but the process around it. Mark demonstrated how important it is to:
- Follow Claude's thinking process — not blindly accept what is being proposed
- Stop in time — as soon as Claude heads in the wrong direction, intervene before technical debt accumulates
- Steer with precision — not start over, but sharpen the context and guide Claude back on track
This is a skill in itself. And it is precisely the skill that juniors currently lack.
The problem with junior developers in the AI era
AI agents regularly do the wrong thing. Not always spectacularly wrong — sometimes subtly. A classic example that came up in the session: adding a sleep statement to fix a race condition.
This is the kind of solution that works in a demo and fails in production. A junior without sufficient context might accept it, because the tests go green. An experienced engineer sees it immediately: this is not a fix, this is hiding the problem.
The point is not that AI is bad. The point is that juniors today need more coaching than ever, not less. They are exposed to more code, more complexity, and more AI output that sounds convincing but can be structurally wrong. Without a strong technical mentor alongside them, the risk is high that they copy bad patterns without realizing it.
What this means for how we work
If you are using AI in your engineering organization — and you are, whether you realize it or not — these are the lessons from Build 2026:
- Domain knowledge remains irreplaceable. Mark could only steer because he understood what the code was supposed to do.
- Stop and reorient early. The further Claude heads in the wrong direction, the more expensive it is to come back.
- Train juniors on the process, not just the output. Teach them to read Claude's reasoning, not just accept the code.
- Sleep statements are a code smell, not a solution. If AI suggests this: stop, and analyze the underlying race condition.
Conclusion
Mark and Scott are seasoned engineers at the top of their craft. And that is exactly what makes this session stand out: instead of another AI hype demo, they show what it actually looks like to use AI responsibly as part of serious engineering.
The gap between vibe coding and world-scale engineering is real. AI does not make it smaller — AI makes it more visible. And the people who can bridge that gap are not those who write the fastest prompts. They are the ones who know when to intervene.
Based on the Microsoft Build 2026 breakout session: Scott and Mark learn... how agents reshape software engineering | BRK247
