Programming to Exceptions

Read the articles

Read Parts 1, 2, and 3 in order: method contracts, exception design, then logging and progress. The concepts apply across languages; the worked examples use C#.

• 

  • Error Handling
  • Method Design
  • Boundary Validation

  Programming to Exceptions, Part 1: Method Contracts and Failure

  Method contracts let callers rely on completed work and let failures propagate. C# examples distinguish retrieval from search, validate domain entry points, and assign handling to its owner.

  28 October 2019Markdown

• 

  • Error Handling
  • Class Design
  • Architecture

  Programming to Exceptions, Part 2: Diagnostics and Boundaries

  Specific exceptions preserve failure meaning, causes, and context. A shallow C# hierarchy, Gateway translation, and middleware enrichment carry diagnostic records across service boundaries.

  28 October 2019Markdown

• 

  • Error Handling
  • Structured Logging
  • Architecture

  Programming to Exceptions, Part 3: Logging and Progress

  Structured logs preserve the facts needed to investigate failures. Application Insights custom dimensions make them searchable, while typed progress events track long-running work.

  28 October 2019Markdown