I am jaded, she told me, and here we are.
I am jaded, she told me, and here we are.
I likely won't be contributing. I am just digging around to see what I can see.
.NET OSS has been a journey!
Happy to say I am still walking it!
dotnet now owns mono. I need to hack at mono. Which means the runtime reposittory.
I am in the upside down.
We raised a $3.5M CAD seed round led by AQC Capital, with participation by well-known angel investors - including @scott.hanselman.com! π
Why raise a seed now? What's ahead?
Read moreπ
About to for the dotnet runtime. I feel strangely far outside of my comfort zone.
No fun. Maybe less cursing? Maybe ... π
One of these days I will learn to read the documentation before I break stuff.
Today is not that day.
One of the things my team owns that I'm VERY proud of is @vscode.dev *for Education.* We just released our authoring tool so you (educator or not) can publish your own courses and lessons AND they'll be saved to your GitHub! Learn more, and please share with educators! vscodeedu.com/whats-new/2326
At the risk of repeating myself. I am not a fan of recursion.
This was a lot of fun!
Thank You again for the opportunity to share my opinions!
Going to watch this tonight!
Let's inspect "The hidden life of method calls" in #dotnet via #CSharp with @kevingosse.net.
Date: 2025-07-09 Wednesday
Time: 17:00 UTC
#2codeOrNot2code
www.youtube.com/watch?v=JhBI...
Duende is committed to open source and values contributors. We are now sponsoring Astro and Starlight, the static site generator that powers our docs.
More details about Astro and why we are sponsoring on our blog: duende.link/astr055 #dotnet #astro #identity
Let me know when the streams are so I can pop in and be a pest
After looking through a few analyzer code fix repos, only a few actually separate those assemblies.
Any traction on the performance testing of analyzers? It's becoming more an more important.
I've got a codebase with over a million lines of C# and I want to test the perf of my analysis.
Also. You continue to use Extensions. Which makes me feel like I am missing how you are using it in context.
Yeah. I was migrating a set of Analyzers when I thought about our conversation. I figured I'd try it and see. It's only Analyzers and CodeFixes, no source generation.
I think I am going to attempt the separation for learning, not sure if I will ship it that way.
I love/hate that you explained it so well and that it's in line with what I was thinking I should do.
I am still a bit shaky on how the separation of the assemblies but the single nuget package gets around the Workspace API problem.
I am sure it will come to me as I am building the package
@flash0ver.bsky.social Okay. So now I am getting to separating Code Fixes and Analyzers in separate assemblies.
Is the thought that I should expect consumers to use two nuget packages?
Or should I find a way to bring them back together under a single package?
I just spent way too much time fixing a "bug" which turned out to be a feature built on design flaw.
It's called exercise or manual labor. It's been around as long as we have.
I am definitely not the authority on that. π€·
I'm only two in as a professional. Three total. I am looking forward to achieving these milestones and excited to have the opportunity to grow between now and six!
The only way to Roslyn.
Embed Card for https://isaacl.dev/gij
Explore how to build MCP remote servers using Azure Functions. #AzureFunctions #MCP
https://isaacl.dev/gij
Embed Card for https://www.coffeeandopensource.com/guest/david-whitney.html
Had a great time chatting with @davidwhitney.co.uk on @coffeeandopensource.com today about all kinds of #tech topics. Video is live on YouTube and podcast is available wherever you find them. Take a look/listen and thanks!
https://www.coffeeandopensource.com/guest/david-whitney.html
Welp. Gotta find a different way to learn German now.
What if you've already had shingles? Asking for me.
As a senior-ish dev. I believe that statement is false.