Writing
A Suite the Team Can Keep Trusting
A growing acceptance suite stays trustworthy through explicit scenarios and owned resources. Organize by feature, keep Act visible, review complete comparisons, and retain useful CI failures.
Topic
Naming
Choosing names that state what a thing is, and keeping those names stable as a value moves through a system.
6 pages
Chapter
Class Design in C#
Internal by default, behavior-only classes against state-only types, the two sanctioned uses of interfaces, and closing concrete descendants.
Chapter
Class Design in Python
Two kinds of class and why that separation holds, no inheritance for extension, and naming conventions for polymorphic types.
Chapter
Naming Conventions in C#
Deriving names rather than inventing them, domain suffixes over indices, the Async exception, and why Retrieve and Search choose different failure contracts.
Chapter
Naming Conventions in Python
Naming a thing for what it is: variables named after their type, methods that state the domain outcome, and why inventing a fresh name at each site is where wrong names come from.
PWI
Architecture with Intent
The Domain Facade exposes business operations while internal classes call one level down. Managers orchestrate workflows and own configuration and service boundaries.