by Jonathan Bright | Nov 10, 2026 | Tutorials
A production C# code review needs a concrete answer to three questions: what behavior does the caller rely on, which change could break it, and what evidence would catch that break? A checklist becomes useful when each answer points to a contract, a test, or an...
by Jonathan Bright | Nov 10, 2026 | Tutorials
A shopper entering six items when only five are available needs a useful rejection. A negative stock count passed by application code needs a different response. Returning the same “invalid input” result for both can hide a defect and send the shopper back to a form...
by Jonathan Bright | Nov 10, 2026 | Tutorials
A BenchmarkDotNet result can compare two methods precisely while missing a more basic problem: the methods answer different questions. Before you use a result to justify a change, establish the required behavior, check both implementations against it, and define...
by Jonathan Bright | Nov 10, 2026 | Tutorials
An API compatibility policy becomes useful when it names a consumer behavior you can test. For a customer response, “the old client still compiles” is too weak: the client might deserialize a response and quietly lose the customer’s name. This tutorial builds a...
by Jonathan Bright | Nov 9, 2026 | Tutorials
A nullable warning should be able to stop a CI build before an unsafe dereference ships. An SDK analyzer can catch a different mistake in the same build: rethrowing an exception in a way that discards part of its stack trace. This tutorial makes both checks fail,...