Search Results

The simplest solution is to NOT have the aggregated list 'allVarOfAs'. Instead make it a method or property which returns the aggregated list on the fly, but doing a SelectMany over aList. E.g. IEnu …

Option 3: Create individual objects corresponding to specific responsibilities, and then have each user hold a collection of these. The collection of responsibilities for a user will contain only the …

First: What is the program supposed to do? You cannot make decision about architecture without knowing the purpose of the program. Also, ignore advice from people whom you haven't told the purpose of …

If the class has no state, you could consider turning it into a function or static method depending on your language.

"Single responsibility principle" is perhaps a confusing name. "Only one reason to change" is a better description of the principle, but is still easy to misunderstand. We are not talking about say wh …

You coworker is right. Internal state should be encapsulated by default and only exposed where there is a good reason to. So when in doubt, hide. Should I really think for each parameter if it mak …

The most effective and helpful way to prevent clients from "misusing" an object is by making it impossible. The simplest solution is to merge Initialize with the constructor. That way, the object wil …

A variable should always have the smallest scope and the shortest lifetime possible. Therefore a class member is preferable to a global variable, and a local variable or parameter is preferable to a c …

Having a class for each query method is not best practice. A core OO design principle is: Classes should have low coupling and high cohesion. Unfortunately, the high cohesion side is often forgotten, …