Writing
Learning a System Through Its Tests
Acceptance tests let teammates learn requirements and production behavior together. Follow one order through Arrange, the visible Act, independent observations, and complete assertions.
Topic
Architecture
How a system is divided into layers, where each responsibility belongs, and what may legitimately depend on what.
11 pages
Writing
Refactoring and Adopting Boundary Testing
A stable Domain Facade lets acceptance scenarios and assertions survive internal refactoring. Adapt test support behind unchanged observations and adopt complete boundary tests feature by feature.
Writing
SOLID IS OLD: Dependency Inversion Needs a Good Abstraction
Dependency inversion needs domain-owned contracts that hide implementation knowledge. Follow a show query from source dependencies through models to a stored procedure.
Writing
Programming to Exceptions, Part 2: Diagnostics and Boundaries
One log record should explain a failure to the support team. Exceptions carry a message, reason, action and context, are translated where meaning is known, and are logged once.
Writing
Programming to Exceptions, Part 3: Logging and Progress
Each failure is logged once at the entry point, with its facts as Application Insights custom dimensions for KQL queries and alerts. A shared progress logger reports long-running work.
Writing
Clean Abstractions Around Libraries
A library boundary owns the application's contract even when its terms match the library's. It contains provider types, validation, failures, and configuration, and keeps replacement possible.
Chapter
Architecture Layers in C#
Structure communicates intent: strict layers from Domain Facade to Gateway, internal by default with a public surface the compiler enforces, and folder depth that marks each class's level of abstraction.
Chapter
Architecture Layers in Python
Structure communicates intent: strict layers from Domain Facade to Gateway, a public surface declared in the boundary __init__.py, and folder depth that marks each class's level of abstraction.
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.
Writing
The Purpose and function of a Data Access Layer
A Data Access Layer isolates business logic from the logical data model through domain-specific methods, stored procedures, and results shaped for the business layer.
Writing
ASP.NET MVC Framework Design Problems
ASP.NET MVC's indirect access to views spreads responsibilities across controllers and templates. ViewData, child actions, and typed view instances frame the critique.