http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660You can embed defaults in the builders instead of putting them in the objects you construct. That keeps your actual objects clean. Builders are priceless for building configuration too. Some examples are AutoFac's ContainerBuilder or the fluent config builders for EntLib. In these scenarios it makes a lot of sense to "feed builders into builders". Think of building a configuration for logging where you build the sub-config for formatting log entries and the like.http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment7http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment7Fri, 26 Oct 2012 06:14:32 GMTOr the fact that he's constructing it. Probably tastes like cardboard.http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment6http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment6Fri, 26 Oct 2012 04:16:00 GMTI like the Builder pattern as it is popular in the Java world: http://www.informit.com/articles/article.aspx?p=1216151&seqNum=2 It allows you to create immutable objects without endlessly writing constructors for all cases. All checks can be conveniently put into the build() method. If you don't mind creating a new builder every time you want to create a new object, there is a simpler way with almost no overhead compared to getters/setters: http://egalluzzo.blogspot.de/2010/06/using-inheritance-with-fluent.html http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment5http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment5Thu, 25 Oct 2012 14:02:38 GMTYes, the example is too simplified and doesn't show real power of Builder pattern. It only shines when used in more complex scenarios or in conjunction with other patterns, like strategy. It is logical to use Builder when code specifying the construction details is actually different than the code that fetches the final result.http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment4http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment4Thu, 25 Oct 2012 12:48:26 GMTI agree with Ayende. In the real world what use a cook in a pizza parlour if he doesn't know how to make an Hawaiian pizza.http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment3http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment3Thu, 25 Oct 2012 10:55:31 GMTI've been using message builders for a long time now and found they bring this to the table: - better semantics/intent (more verb-y than noun-y), - making a construct that is immutable, mutable for the duration of its construction, - allow different parts of the code to contribute to the building processhttp://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment2http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment2Thu, 25 Oct 2012 10:49:55 GMTI find this pattern priceless when working with legacy code.http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment1http://ayende.com/159362/design-patterns-in-the-test-of-time-builder#comment1Thu, 25 Oct 2012 10:45:34 GMT