Contents tagged with Design Principles
-
Do your features fit together?
Today a was listening to the great Q&A session with Anders Hejlsberg. But the post is not about the session itself, the thing that touched my ‘heart' is that he mentioned a great point about the language design. There was a question to him about a missing feature in C#, and his answer was that a language is not (only) about features but it is more about "how all the features do they play together".
-
Domain-Driven Design: Two basic premises
In the post I want to discuss about two basic Domain-Driven Design premises which stand on the base of all other DDD principles, patterns, and practices. DDD principles, patterns, and practices described by Eric Evans are not something invented by him, but are something that were discovered and used long experience path by many folks. So, all DDD goodies have just two simple premises which I will cover in the post.
-
Builder Pattern and Fluent Interface
In the post I want to discuss the practical part of the Builder pattern and how builder pattern usage and implementation can be simplified by Fluent Interface, it will show how these two patterns can leave in harmony with each other.
-
With modern tools, Is a solution\project structure important?
OK... VS.NET + ReSharper are powerful... but that is enough?
-
Domain Driven Design: Learning
1. Introduction
-
Separation of Concern vs Single Responsibility Principle ( SoC vs SRP )
These two great principals that stands on the base of many design and architecture decisions. We very often meet these principals in book, articles, blogs, etc... And main question which risen in my head was what they really all about and how they relate to each other? These two principles are totally discrete from each other or their core principle is the same?
Just to remember what these two principles means lets read following statements which defines the each of them: