Pages

▼
Showing posts with label behaviour driven development. Show all posts
Showing posts with label behaviour driven development. Show all posts
Tuesday, 18 December 2012

Technical Details as Part of Domain Model

›
Dear Junior A classical questions in Domain-Driven Design is whether technical details should be part of the domain model. The usual an...
Wednesday, 14 March 2012

DRY and False Negatives

›
Dear Junior In earlier letters we have talked about the DRY-principle, how looking for duplicated code can help finding violations of DRY ...
Wednesday, 7 March 2012

DRY and Duplicated Code

›
Dear Junior In my last letter I wrote about how the DRY-principle (Don't Repeat Yourself) talks primarily talks about the number o...
Thursday, 1 March 2012

DRY is about Ideas, not Text

›
Dear Junior Ever since the Pragmatic Programmer, the principle of DRY (Don't Repeat Yourself) has been one of the central pieces of...
Friday, 16 September 2011

Public final and data encapsulation

›
Dear Junior We were discussing immutable value objects and using "public final" data-fields for their representation. In tha...
Monday, 12 September 2011

Public final is also Immutable, Again

›
Dear Junior I must apologise as in my last letter I mixed two separate discussions into one: one about immutability, and one about encapsu...
Wednesday, 2 February 2011

Conceptual Abstraction, and Technical

›
Dear Junior I think there is an important distinction between solving a technical problem and solving the conceptual problem. And...