I have a peculiar situation.

I asked this question and someone answered the question well by saying that the implementation I was planning on using is more of an anti-pattern as it is not addressing the problem and suggested using single-responsibility (which technically is the way it is currently implemented) so I marked this as correct.

My problem here though is that another person answered suggesting that instead of using what I am, use a builder pattern with chained methods. I said I didn't like that idea because there wasn't any way to specify mandatory fields but then someone else commented on that answer with a solution which uses the builder pattern and allows for mandatory fields which are obvious to a developer using the object.

I personally think that the commented solution is a much better solution to the problem that I described, but the question was, what is this pattern.

So who should get the points? The original accepted answer. The person who suggested the builder pattern because in the comments to that answer is the solution. Or whether I should ask the person who commented to write that as an answer?

Please help me as I want to make sure anyone else who comes across this post has the best advice.

  • Thanks that is really useful. So basically it sounds like I should create my own answer which is a combination of both answers on the post and the comment. I wasn't sure whether this would be frowned upon in the community but by the looks of that post you shared it seems like the better option.
    – Keithin8a
    Jul 21, 2015 at 11:53
  • 3
    just make sure that your answer 1) looks good (otherwise people will vote it down) 2) can stand on its own (not as "see <this link> and <this link>") and 3) has proper attribution to answers and comments it builds upon
    – gnat
    Jul 21, 2015 at 11:57
  • you really got to click and read the link in prior comment, at words "can stand on its own"
    – gnat
    Jul 22, 2015 at 10:59


You must log in to answer this question.

Browse other questions tagged .