Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • In one of the episodes Uncle Bob said that changing switch statement in one dll affects the depenedent dll and causes rebuild and redeployment. But why? Or maybe I just misunderstood his thoughts? Commented Mar 18, 2013 at 18:56
  • You'd have to ask Bob that. But generally too many dependencies are the cause. If there's no dependency on the other DLL, or your change isn't a binary breaking one, there's no redeployment of the other DLL needed. Commented Mar 18, 2013 at 19:13
  • @EngineerSpock usually a switch statement will perform different logic based on an input parameter. If the cases are built around implementation classes, and a new class is added but the switch statement isn't, what should be the expected behavior? It's a violation of OCP and also means it's tightly coupled to the implementing classes. Commented Mar 19, 2013 at 2:34