For most of my career, I’ve been a proud Windows developer.
I build Windows apps. I run Windows as my primary dev machine. It’s been home.
But recently? That’s been challenged — not by another OS, but by AI.
Developer workflow is changing fast. Agents, containers, automation — they’re reshaping how we build software. So let’s rewind a little, talk about why Windows, and then look at what’s shifting under our feet.
Why Windows?
There are really two answers.
1️⃣ The Tools — Visual Studio
For years, Visual Studio was untouchable.
While others were sprinkling Console.WriteLine or scanning logs, Windows developers had:
- Step-through debugging
- Deep variable inspection (even the gnarly ones)
- Conditional breakpoints
- Edit-and-Continue (Hot Reload)
- Integrated build, test, and profiling
It wasn’t just an editor — it was a command center.
And honestly? It still is when I need serious debugging power.
2️⃣ The Stack — XAML and Beyond
The second reason: the Windows UI stack.
Since the early days of WPF and Silverlight, I’ve loved XAML. Declarative UI. Clean separation. Powerful binding.
As the platform evolved — WPF → Win8 → UWP → WinUI — XAML stayed central.
Now with the Uno Platform, that same XAML lets me target:
- Windows (WinUI & Desktop)
- macOS
- Linux
- Android
- iOS
- Web (WASM)
One UI definition. Everywhere.
Pair that with MVVM and you get a clean, structured architecture. Add MVUX from Uno and you get a reactive, modern state management model.
It’s simple. Powerful. Productive.
So What Changed?
For the first time in my career…
I’m not building for WinUI first.
That used to be my workflow:
- Build and debug on WinUI
- Then test on other Uno targets
But when Uno recommended the Skia backend, things shifted.
Now I default to the Desktop target (Windows, macOS, Linux). Why?
- Faster build and launch
- Clearer XAML errors
- Better day-to-day debugging flow
Ironically, building for Windows became less about WinUI itself.
And that shift matters — because an even bigger shift was coming.
Enter AI Agents + App MCP
This is where things really changed.
With AI agents — whether it’s Claude, Copilot, or Codex — and the Uno Platform App MCP:
An agent can:
- Build the app
- Run it
- Take screenshots
- Verify changes
- Repeat across Desktop, Web, and Mobile
I can now assign an entire issue to an agent.
It will:
- Plan the solution
- Implement it
- Run the app
- Validate the outcome
Across multiple platforms.
That’s not autocomplete.
That’s delegation.
Containers, YOLO Mode, and Dev Isolation
The next evolution?
Running agents in YOLO mode inside a dev container.
I’m using:
- A Linux container
- Running on WSL
- Connected via VS Code
The dev container stays locked down:
- Limited GitHub access
- Controlled environment
- Isolation from the host
I can still launch desktop and web targets for debugging — but the agent operates in a contained sandbox.
It’s structured chaos.
Where That Leaves Me
So here I am.
Still using Windows.
Still building for Windows.
But not the way I used to.
Visual Studio is now my “serious debugging” tool.
Day-to-day development?
Often handled by an AI agent — inside a container — through whatever console I happen to be using.
That’s a massive shift.
The Bigger Picture
AI isn’t just speeding up development.
It’s redefining the workflow.
Agents. Sub-agents. Teams of agents.
Parallelizing feature work.
Burning down backlogs.
Testing across platforms automatically.
The tooling and models are evolving monthly.
Six months from now? The workflow may look completely different again.
One thing is clear:
Being a developer today isn’t just about writing code.
It’s about orchestrating intelligence.