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
  • How different are each of the products? Are they different enough where you really need separate classes, or can you just use one Product class with a ProductName property? Commented Jan 22, 2015 at 17:25
  • they are fairly different I would say. for example, each has its own unique properties (several) and some computations differ as well. So if I use one Product class I'd need to have a differentiation on when can I use set of properties for product A, when for product B and so on, while leaving non-active properties unused. Commented Jan 22, 2015 at 19:19
  • 1
    In response to your comment about not needing to refactor: only refactor when there is a reason that involves making the software better. Refactoring to make bugs easier to find and fix is a valid reason, as is refactoring to reduce coupling such that fixing one bug does not cause two more. Go forth and refactor this code with the blessing of the Internet! Commented Jan 22, 2015 at 22:57