Week 25, year 2016
- What’s going on here? - Question: What is more exasperating than reading design documentation that doesn’t synch up with the code? One answer: Writing such useless design documentation. Another answer: Writing documents that don’t stand a chance of being aligned with the code. My answer: … Continue reading → [The Responsible Designer]
- Welcome! - Just starting out with Domain Driven Design? You’re just getting into Domain Driven Design (DDD), Command Query Responsibility Separation (CQRS), and Event Sourcing (ES) and most of the overall principles are clear… but as soon as you start using them in your own domain - everything becomes a decision-making nightmare… You start having conceptual problems modeling your application. Your model starts to get polluted. You don’t know if your Aggregates are reasonable. [DDD Weekly]
- C# functional extensions NuGet library - I’ve created a NuGet package out of the functional extensions I wrote about in this post series and in my Pluralsight course. C# functional extensions NuGet library Thanks to one of the listeners of my Functional C# course, I finally made a separate NuGet package which is based on the Result class I wrote about awhile ago. The package contains the following classes: Result ResultExtensions [Enterprise Craftsmanship]
- Pragmatic integration testing - The topic described in this article is part of my Unit Testing Pluralsight course. When trying to break down unit testing, the bigger picture stays incomplete if you overlook the subject of integration testing. In this post, we’ll discuss how to make the most out of your integration tests with pragmatic integration testing. Integration tests are tests that, unlike unit tests, work with some of the volatile dependencies directly (usually with the database and the file system). [Enterprise Craftsmanship]