Thomas, I'm sorry I never saw your post or replied. FWIW, thanks for all the great thoughts. Now I'm the one curious on where your journey ultimately took you! At the time, I think I would have concurred with you that the value wasn't there yet. And, with all the supply chain issues, I'm not sure if it's really improved much. One of the drivers for my overhaul was that I wanted to experiment with a DIY SSD NAS with 10G bandwidth. Ended up kludging together an Intel NUC-based setup using TrueNAS Scale that I was moderately happy with, except that the NUC kept shutting off. Haven't come back to debugging that problem yet. I also had headroom from my ISP to go to 2.5 or 5 gbps, which factored into into my decision. Ultimately, I upgraded to 2.5, and then was stuck with the choice of using the Firewall Purple for all or just some network traffic. Anyhow, curious to know how your setup has evolved over the last couple years. Sorry again for ghosting you! David

Short update - here's a picture of the somewhat organized Firewalla setup. I also ended up setting up my Intel 8th Gen NUC with a Sabrent 10G Thunderbolt 3 adapter

Nice post. It gets even simpler with .Net 6: "Building Minimal APIs In .NET 6 - .NET Core Tutorials" https://dotnetcoretutorials.com/2021/07/16/building-minimal-apis-in-net-6/

It's one of the places the compiler uses duck-typing...no interface needed. Would be great to have this type of shape-based coding pattern more available to the developer, sometimes called "structural typing." The father of C#, Anders Hejlsberg, said that the benefits of structural typing was a big take-away for him when he subsequently designed Typescript.

Nice post! I agree with most points, but have to disagree with the absolute statement "don't do X, ever." There's always context and I've definitely at times made things more complex than they need to be. "Overengineering" can be a problem, too, most often because you don't know the requirements of the next two or three needs of a feature, so you're likely going to have to refactor again. Many times, it's better to wait for two or three examples to remove the hard-coded number or refactor the shared logic block/method. Also, a quick shout out to Martin Fowler's excellent book on refactoring , which is in it's second edition. Anyhow, keep up the great posts!

Same!

Chris Bongers thanks! Just getting started!

Cheers to the idea of public learning. It's what inspired me to start blogging, too. My tagline is, "Let's learn new things, together."

Mireli Eyyubzade Same concern here. Syed Fazle Rahman any info on whether this will be added?

Looking forward to C# 10. Is there a way to start using it today in VS Code or Visual Studio?