There’s no reason that you shouldn’t be able to do… if (false) { bool x = false; } bool x = true; …but you can’t. The reason you can’t is because MS considers the second declaration of x to have overlapping scope with the first, even though there isn’t a…

Unless you’re living under a rock, you’ll be aware that most language designers (Microsoft’s included) regret the existence of null. …

Okay, I’m calling out a specific implemenation here, but this is an issue I have with counting semaphores as a whole. …

Whatever fucking retard did the user testing on VS IntelliSense and still let that shit ship should be put against the wall. We often have variables named the same as classes, like… MSKnobGobler msKnobGobbler = new(); … because, you know, THAT’S THE FUCKING RECOMMENDATION. So when we start typing ‘m’…

We’ve all seen it. That guy who creates objects like… public record Employee { public string Name { get; init; } public int Age { get; init; } public int IQ { get; init; } } …and initializes them like… var employee = new Employee { Name =…

Dear Microsoft, I’m sick of writing nameof(…) every second fucking parameter in validations. Can you fix this shit already? So you’re all familiar with ArgumentException I. Should. Fucking. Hope. It’s what you throw (or the base class of what you throw) when some diversity hire passes an invalid value to…

IEnumerable<T> is a sexy little beast and we use it all over the place. For the retards amongst you, it’s a collection of sorts, but not necessarily one that currently exists or is finite. What it really is, is a hook to an enumerator. …

Microsoft really fucked the dog on this one. Say you have some class… public interface ICalculator<T> { T Add(T augend, T addend); T Subtract(T minuend, T subtrahend); T Multiply(T multiplicand, T multiplier); T Divide(T dividend, T divisor; } … but your implementation needs to be called asynchronously because it takes…