Software design
Designing software that lasts: Domain-Driven Design, error handling and choosing the right abstractions, with examples in Java.
Series
- Series Pragmatic DDD 3 of 3 parts published
Domain-Driven Design without dogma: when it pays off, the four layers in Java, testing, error handling and moving an existing codebase towards a rich domain.
- Series Error Handling in Java 2 of 2 parts published
How exceptions work and how to design them, the mistakes to avoid, and the modern tools: Scoped Values, structured concurrency and the Result type.
Featured
All posts
- Pragmatic DDD in Practice: Testing, Errors, Migration and Pitfalls
- The Four Layers of Pragmatic DDD: Code, Packages and Java 25
- Pragmatic DDD: When It Pays Off and When It Doesn't
- Abstract Class vs Interface: The Architecture of Intent
- Modern Java Error Handling: Scoped Values, Structured Concurrency and Result
- Java Exceptions: How They Work and How to Design Them