Reputation
45,142
Next tag badge:
151/100 score
16/20 answers
Badges
13 111 203
Newest
 Nice Answer
Impact
~1.5m people reached

Apr
24
comment A software design pattern to model runtime-dependent behavior
@KeithS: In fairness, the State pattern looks exactly like the Strategy too. Patterns are broadly separated by intent, not by implementation.
Apr
24
comment A software design pattern to model runtime-dependent behavior
I honestly suspect your interviewer was just looking for an answer that he could get you to expand on, to prove that you knew what you were talking about.
Apr
24
comment A software design pattern to model runtime-dependent behavior
Ahh, now that's a good answer.
Apr
24
comment A software design pattern to model runtime-dependent behavior
@Telastyn: A Strategy enables "the application to create different classes for display at runtime depending on the platform". Whether that creation is done via Factory Method or constructor is largely irrelevant. That said, I would have been sure to mention Factory Method as well, just in case there was a miscommunication.
Apr
24
comment A software design pattern to model runtime-dependent behavior
Disagree. Abstract factory is an abstract object that returns other objects, which combine to make an implementation, such as my answer to this question: programmers.stackexchange.com/questions/81838/…. This is only two cases, so there is no need for multiple components like that. A Strategy was the answer, possibly combined with a Factory Method. I'm not sure why Oded deleted his answer.
Apr
23
comment Is there a need for a factory class for creating viewmodels?
@MattDavey: Can you wrap those two comments into an answer that I can upvote?
Apr
23
comment Pattern for select case on object type (of interface)
@KingOfHypocrites: You're completely missing the point of select as a code smell. Nobody has ever said that it should be avoided completely, only that it should be isolated to its own method and kept to one line per case. This is generally done using a factory method which returns a strategy, but if your situation isn't complex enough to justify that then don't.
Apr
23
comment Are any companies moving from DVCSs to CVCSs?
Your original comment. Or maybe I should say "answer". "CVCS tools provides strong authorization and authentication features, faciliting their integration with the existing LDAP ... DVCS tools don't." Both parts of this are misleading at best, untrue at worst. SVN does not hook into LDAP without a wrapper any more than Hg does.
Apr
23
comment Are any companies moving from DVCSs to CVCSs?
@VonC: "my only point is Git or Mercurial alone have no authorization or authentication in them." That is not implicit in your original comment, which is why you've had so much reaction to it. Your implication is that by choosing a DVCS, you have to do without authentication. I would argue that wrapping RhodeCode around Hg is much easier than hooking SVN into LDAP via Apache, so if you don't want yet another password to remember, Hg might be the better choice.
Apr
22
comment Are any companies moving from DVCSs to CVCSs?
Doesn't RhodeCode with Mercurial pretty much solve the authentication problem?
Apr
21
answered Replace Type Code with Class (From Refactoring [Fowler])
Apr
17
comment With continuous integration in .NET, is it acceptable to reference DLLs of rarely-changing assemblies?
@YamMarcovic: How many projects do you have?
Apr
17
comment With continuous integration in .NET, is it acceptable to reference DLLs of rarely-changing assemblies?
@smdrager: Again, you don't have to only build one solution in CI. And, if you want to go down that road, look into NuGet. You won't be sorry.
Apr
17
comment With continuous integration in .NET, is it acceptable to reference DLLs of rarely-changing assemblies?
@YamMarcovic: I have seen this effect, but not so much with the latest version (unless you have Resharper installed on a less-than-optimum machine). But, if you are suffering from this problem, you can still leave them in separate solutions and build them as part of the CI build.
Apr
17
answered With continuous integration in .NET, is it acceptable to reference DLLs of rarely-changing assemblies?
Apr
16
awarded  Nice Answer
Apr
16
awarded  Nice Answer
Apr
6
awarded  Popular Question
Apr
4
answered How to change documentation expectations from “risk management” to a “project risk”
Apr
3
comment Do I have to deliver my utility and helper code to clients?
@deviDave: Did you get paid for the months you were working on those libraries? If you did then I don't see that you have much to complain about if the customer finds another use for them.