It follows the fold now 🚗 !
Early UIHinge support in testing with @UnoPlatform, the fold drives everything you see here 👀
Experimental work ahead of the iPhone Duo landing
#dotnet#iphoneduo#ios27
Six years later, my Surface Duo sample is now running on iPhone Duo 👀
Updated to latest @UnoPlatform, nothing additional written for the Duo. Same app on Android, web & desktop
Can't wait for the .NET UIHinge bindings so the car follows the fold 🚗
#dotnet#iphoneduo#ios27
DAY 2, LET'S GO, ORLANDO! 🚀🔥
We're back at #VSLive, and the Uno Platform Studio challenge is still on!
Already fired up Studio and started building? Swing by the booth, show us what you've been working on, and claim your t-shirt + mug!
Haven't had a chance yet? There's still time to dive in, build something, and walk away with some swag.
Let's see what you've got! 😎
Day 2 of #VSLive and I'm still looking for developers who've put Uno Platform Studio to the test.
Built something? Come find me at the booth. I want to see it!
Haven't tried it yet? Give Studio a spin and swing by. We've got t-shirts and mugs with your name on them! 😎
Most AI coding mistakes get caught late, in review or after a build breaks. Stopping them earlier costs less.
I'm hosting a table topic at #VSLive on how teams do this. Bring your notes and we'll compare.
Catch It Earlier: Prevention over detection
“Verifying it is the hard part.”
Exactly why we’ve evolved Uno Platform Studio in our latest release into a workbench where .NET developers and AI build and ship software together.
The validation part of the loop is CRUCIAL.
Have a listen to this latest interview with Satya.
What does software engineering look like when generating the code becomes cheap and verifying it is the hard part? A rare podcast focused on everything around building software, with @satyanadella. Timestamps:
00:00 Intro
02:12 Microsoft’s open-source shift
04:15 Building VS Code in the open
05:55 Copilot, Cursor, and Claude Code
09:52 Decision engines
12:32 Verifying AI-generated code
15:39 The software factory
20:45 Bringing AI to existing products
24:06 Why adopting AI is different to adopting React
26:29 The changing role of software engineers
29:25 Microsoft’s voluntary exit offers
34:05 AI anxiety and changing roles
36:35 Junior hiring
42:36 Open models
45:39 Owning your AI infrastructure
51:21 Building trust in AI agents
53:48 Local models and hybrid intelligence
56:39 Microsoft’s model strategy
59:26 Advice for engineers
1:01:21 Closing takeaways
Brought to you by:
• @turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable. turbopuffer.com/pragmatic (I built a greatly improved podcast/newseltter search with it, check it out: pragmaticengineer.com/search)
• @linear – the product development system for teams and agents. linear.app/pragmatic
• @WorkOS – everything you need to make your app enterprise-ready. workos.com/
3 interesting takeaways from Satya:
1. A new form of software engineering: teams building software factories to improve their work.
Satya cites the Azure networking team which manages 500+ fiber network operators and recently built an agentic system to better manage emails and processes. Now, they operate much more efficiently as a result. Satya sees this as the reality of “AI transformation”: brownfield work on building software factories to improve how teams operate, all while continuing the day-to-day work.
2. “Own the intelligence”: avoid lock-in & treat agents as an insider risk.
Satya cautions companies to avoid lock-in with any single model provider by ensuring that the harness, memory, and model are not coupled, so that they can be changed with ease. He also thinks more companies should consider using open models as a way to protect their core intellectual property (IP) from leaking out, and build private evals to decide what models to use and upgrade to. He also says that models are intelligent but unreliable, so it’s best to treat them as “insider risks” and build a separate system to verify that agentic systems work as expected.
3. What’s with those voluntary exit offers?
I asked Satya directly why Microsoft recently made voluntary exit offers to most of its software engineers for the first time in the company’s history. I also wanted to know if it could mean layoffs in the future. Unsurprisingly, his reply was diplomatic, but in the podcast I rehashed what I heard in a more direct way.
Using Claude Code or Codex on .NET?
dnx agentic.check picks the right skills for your repo (MVVM vs MVUX, XAML vs C# Markup, Fluent vs Material, Uno.Sdk version) from dotnet/skills, Uno Studio and more, then keeps them updated.
Check out @vincenth_net 👇
github.com/VincentH-Net/dotn…