Managing Errors

2. Implementation Loop

1. Plan: Choose the pattern (Retry, Circuit Breaker, Fallback).
2. Validate: Ensure the error propagation doesn't swallow context or stack traces.
3. Execute: Apply consistent error types/classes.
4. Test: Write a failing test that triggers the error condition.

Instructions

Core Principles

• Fail Fast: Validate input early.
• Preserve Context: Always include stack traces and relevant metadata.
• Meaningful Messages: Explain what happened and how to fix it.
• Don't Swallow Errors: Log or re-throw; never ignore silently.

Pattern References

• Circuit Breaker: Use to prevent cascading failures in distributed systems.
• Error Aggregation: Collect multiple errors (e.g., in forms) instead of failing on the first one.
• Graceful Degradation: Fall back to cached data or local defaults when services fail.

See detailed patterns in resources/patterns.md

Language-Specific Implementation

For concrete code examples in Python, TypeScript, Rust, or Go: See language examples in examples/concrete-code.md

Resources

• resources/patterns.md: Detailed logic for modern error patterns.
• examples/concrete-code.md: Templates for custom exception hierarchies and Result types.