Brackeys is your friend. Great Unity and C# content. youtube.com/playlist?lis...

For example, it encourages using constructors and IDisposable instead of magic attributes. Richer as in to has about twice as many assert methods and overloads as other libraries. But MSTest and NUnit have caught up to it a lot over the past few years, so any, really, are a good choice.

Also better at catching otherwise hard-to-find async deadlocks.

I find it more idiomatic to .NET with richer assertions.

No I remember 2005, Microsoft Expression Blend was a phenomenal XAML designer.

Default values are syntactic sugar for calling methods. The compiler fills in missing arguments at the call site. At runtime, most libraries just try to call the parameterless constructor, and don’t go through the trouble of looking for an overload with default values on all the parameters.

Further discussion on this topic: github.com/NuGet/Home/d...

lol, like .NET devs referring to Apple’s OS? OSX (pronounced both O-S-Ex and O-S-Ten), Mac, Mac OS, MacOS, macOS… 🤷‍♂️

There was a grassroots campaign to #DropTheDot a few years ago. But it just bifurcated things.

Neither. It’s dotnet or .NET

Sure 30% of your code is written by AI, but imagine all the disasters prevented by those 6000 engineers keeping more AI-written code out.

Makes sense. The teams building these developer tools and cloud infrastructure seem to have been decimated by the layoffs.