Full Span<Tee> shirt #span #dotnet

Interested in working in .NET Tooling? My team is hiring for a few roles. This is a great to impact the .NET ecosystem, work with devs all across Microsoft and help drive the .NET platform forward. jobs.careers.microsoft.com/g… jobs.careers.microsoft.com/g…

Hey #dotnet people! Exciting news! I've launched my YouTube channel: "Dissecting the Code". It's going to be very similar to my blog, where I'll cover .NET internals, performance tips & tricks, and more deep dives. #csharp I've already published the first two videos: ➡️ Episode 0: What You'll Learn Here ➡️ Episode 1: Dissecting Variable Lifetime I hope you'll like it! Please share, subscribe, and let me know what you think! Your support means a lot to me. 🙏 Links to the channel & videos are 👇

We’re about to take C# to the next level. Look out Python 👀 #dotnet #csharp

Want to see what went down at Update Conference Prague? Watch the highlights and get ready for next year’s edition! 🎉    More than 40 sessions, top experts, and endless networking opportunities - online or in person.   ✅ Save the date for next year: 13-14 Nov 2025! 🔗 updateconference.net   #UpdateConference #TechEvent #DeveloperLife #Networking #SoftwareDevelopment #Learning #TechConf @itixocz @riganti

College teaching of compilers turned me off them entirely. Specifically avoided them when I joined Microsoft. I only ended up on compilers because I was following managers I trusted and respected. Turns out production compilers are so much more interesting and fun.

Microsoft has open sourced its new cross-platform virtual machine layer written in Rust: github.com/microsoft/openvmm From many of the same team who created WSL, including @benhillis.

Not one, but two sessions from @jaredpar at #UPDATECONFERENCE 🚀🔥 Prepare yourself for innovative insights 👉 bit.ly/UCP24SCHEDULE #CSharp #DotNet #OpenSource #UpdateConf @Microsoft

You can also get Hello World in C# in 5 min with this one installer dotnet.microsoft.com/en-us/l…

We get some pretty insane mileage out of .NET as a platform that Microsoft itself builds on top of. You would not believe the types of edge case bugs we find in the platform as a result (compiler, toolchain, runtime, GC, JIT). Dogfooding continues to be extremely valuable to building a robust platform. #dotnet

Hurray - new version of Azure Cosmos DB SDK supports using System.Text.Json just by setting UseSystemTextJsonSerializerWithOptions in the settings: github.com/Azure/azure-cosmo…

Really excited to be speaking at Update again this year. Had a blast last time I was there and expecting good times again!

that

A blast from the past! ❇️ Below is a talk I gave to Microsoft Research in 2013 about what made Midori special. It covered software isolation, safe concurrency, user mode drivers, the app model and more. I like that WalkingCat calls me "young"; for the record I'm not dead yet.

Working on C# has really driven home for me that languages are defined by the ecosystem of tools that support them. A language with just a compiler is basically a toy.

All the conservative discourse about C# language changes misses the fact that the reason C# doesn't have a successor language is precisely because it has changed over time. It's one of its strongest qualities - adapting to be capable of new expressions and contexts.

Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C is hard” issue and it damn well isn’t an DEI one.