Nullable reference types: null-forgiving operator hides real null bugs

The null-forgiving operator (!) suppresses compiler nullable warnings but does not add any runtime null check. Developers use it to silence warnings quickly, masking genuine null dereference bugs that surface at runtime.

Investigate why the compiler warns instead of suppressing with !. Common patterns:

// BAD — silences warning but throws NullReferenceException at runtime
public string Name { get; set; } = null!;

// GOOD — initialize properly
public string Name { get; set; } = string.Empty;

// GOOD — make truly nullable and handle it
public string? Name { get; set; }
public void Print() => Console.WriteLine(Name ?? "(no name)");

// Acceptable null-forgiving: value set by framework before use (e.g. EF navigation)
[Required]
public string Name { get; set; } = null!; // EF sets this before any code runs

Enable nullable globally and treat warnings as errors:

<Nullable>enable</Nullable>
<WarningsAsErrors>nullable</WarningsAsErrors>

The ! operator is a compile-time annotation only. The CLR has no knowledge of it. If the value is actually null at runtime, a NullReferenceException still occurs.