To those who have been living under an anti-Microsoft-news rock for the last few days, .NET 6 and all of its associated goodies have arrived, bringing with it C# 10, performance improvements and a boatload of new features.

Talk about .NET to anyone outside of the ecosystem (and some in it) and you’ll find they’re still confused by “what means what”, will ask “which version do I need” and will oft’ respond “is that the language you have to pay for the IDE to use?” to any news about it.

Unit tests are tests that should test an individual section, or unit, within your code.

For a long time now, unit tests have been preached as the golden standard in most software development communities. They usually come hand in hand with another development concept: mocking. Mocking is where you ‘fake’ a dependency of the unit that you are testing, so you can test your unit in ‘isolation’.

I think the over-hyped importance of unit tests and mocking is a fallacy that is based on purism and idealism over pragmatism, realism and experience that often ends up biting you in the backside when you come to refactor only unit tested code.