Rodney Littles, II
rlittlesii.bsky.social
Rodney Littles, II
@rlittlesii.bsky.social
.NET Developer, Xamarin Enthusiast, Flutter Dev, Dev Ops, Kung Fu Practitioner, and student of the game. My brain, my thoughts!
I am jaded, she told me, and here we are.
October 24, 2025 at 2:28 PM
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!
September 3, 2025 at 7:15 PM
dotnet now owns mono. I need to hack at mono. Which means the runtime reposittory.

I am in the upside down.
September 3, 2025 at 6:07 PM
Reposted by Rodney Littles, II
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👇
We raised a $3.5m CAD Seed Round! Open-source .NET FTW!
Uno Platform raises $3.5M CAD seed funding led by AQC Capital with support from Scott Hanselman, fueling open-source .NET innovation and AI tools.
platform.uno
September 3, 2025 at 5:35 PM
About to for the dotnet runtime. I feel strangely far outside of my comfort zone.
September 3, 2025 at 4:53 PM
No fun. Maybe less cursing? Maybe ... 😆
August 29, 2025 at 6:22 PM
One of these days I will learn to read the documentation before I break stuff.

Today is not that day.
August 28, 2025 at 10:12 PM
Reposted by Rodney Littles, II
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
Visual Studio Code for Education
Visual Studio Code for Education. Powering the next generation of developers.
vscodeedu.com
July 28, 2025 at 9:09 PM
At the risk of repeating myself. I am not a fan of recursion.
July 29, 2025 at 3:32 PM
This was a lot of fun!
July 24, 2025 at 8:17 PM
Thank You again for the opportunity to share my opinions!
July 21, 2025 at 8:29 PM
Going to watch this tonight!
July 18, 2025 at 4:11 PM
Reposted by Rodney Littles, II
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...
2code ^ !2code [S2025E07] .NET Method-ologies
YouTube video by FlashOWare
www.youtube.com
July 8, 2025 at 6:48 AM
Reposted by Rodney Littles, II
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
Duende Software Docs
Get started building your .NET applications with IdentityServer, Backend-for-Frontend (BFF) and our open-source tools.
docs.duendesoftware.com
July 3, 2025 at 3:31 PM
Let me know when the streams are so I can pop in and be a pest
July 1, 2025 at 5:01 PM
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.
June 18, 2025 at 5:21 PM
Also. You continue to use Extensions. Which makes me feel like I am missing how you are using it in context.
June 17, 2025 at 4:05 PM
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.
June 17, 2025 at 4:03 PM
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
June 17, 2025 at 3:39 PM
@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?
June 16, 2025 at 8:30 PM
I just spent way too much time fixing a "bug" which turned out to be a feature built on design flaw.
June 16, 2025 at 7:37 PM
It's called exercise or manual labor. It's been around as long as we have.
May 1, 2025 at 6:33 PM
I am definitely not the authority on that. 🤷
May 1, 2025 at 6:33 PM
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!
May 1, 2025 at 5:22 PM
The only way to Roslyn.
April 30, 2025 at 5:42 PM