tag:blogger.com,1999:blog-7409597408023081712.post4620042617703541348..comments2026-04-07T14:50:10.010+02:00Comments on Random Thoughts on Java Programming: Trainwreck vs. Method ChainingTurbohttp://www.blogger.com/profile/05959847299811800007noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7409597408023081712.post-43036742765285413672016-04-28T11:52:26.254+02:002016-04-28T11:52:26.254+02:00Agreed. It's a bad example. I shall write a bl...Agreed. It's a bad example. I shall write a blog post about a proper builder pattern. (Though Martin Fowler beat me to it. ;-) )Turbohttps://www.blogger.com/profile/05959847299811800007noreply@blogger.comtag:blogger.com,1999:blog-7409597408023081712.post-42070715906194017372016-02-04T16:37:08.635+01:002016-02-04T16:37:08.635+01:00I see where you are going but I don't complete...I see where you are going but I don't completely agree with the example you used for method chaining. A setter normally is a mutator and would not return an object unless you are using the builder pattern. Unless you explictly indicate that you are using this pattern, your intent would be potentially confusing for someone coming back to look at the code.Anonymousnoreply@blogger.com