Take advantage of the null object pattern in .NET to eliminate the need for null checks and avoid runtime errors in your applications.

Take advantage of the open source library Serilog to log your ASP.NET Core application’s data to SQL Server or another database target.

Null means "undefined" in SQL, so numerous online services don't think Christopher Null exists.

How does one avoid the semantically wishy-washy use of NULL-surrogates and instead, actually design structures wherein NULLs are not necessary?