Name for Osherove’s modified singleton pattern?
I’m pretty well sold on the “singletons are evil” line of thought. Nevertheless, there are limited occurrences when you want to limit the creation of an object. Roy Osherove advises,
Does Liskov Substitution Principle also apply to classes implementing an interface?
LSP states that classes should be substitutable for their base classes, meaning that derived and base classes should be semantically equivalent.
“Never do in code what you can get the SQL server to do well for you” – Is this a recipe for a bad design?
It’s an idea I’ve heard repeated in a handful of places. Some more or less acknowledging that once trying to solve a problem purely in SQL exceeds a certain level of complexity you should indeed be handling it in code.
Object oriented wrapper around a dll
So, I’m writing a C# managed wrapper around a native dll. The dll contains several hundred functions. In most cases, the first argument to each function is an opaque handle to a type internal to the dll.
Where ORMs blur the lines between code and data, how do you decide what logic should be a stored procedure, and what should be coded?
Take the following pseudocode:
Help identify the pattern for reacting on updates
There’s an entity that gets updated from external sources. Update events are at random intervals. And the entity has to be processed once updated. Multiple updates may be multiplexed. In other words there’s a need for the most current state of entity to be processed.
Help identify the pattern for reacting on updates
There’s an entity that gets updated from external sources. Update events are at random intervals. And the entity has to be processed once updated. Multiple updates may be multiplexed. In other words there’s a need for the most current state of entity to be processed.
two ways of doing the same thing, what is preferred?
I have some context
then I can do:
with context.getError(Object): ErrorHolder
What is the point of using DTO (Data Transfer Objects)?
What is the point of using DTO and is it an out dated concept? I use POJOs in the view layer to transfer and persist data. Can these POJOs be considered as an alternative to DTOs?
Combining template method with strategy
An assignment in my software engineering class is to design an application which can play different forms a particular game. The game in question is Mancala, some of these games are called Wari or Kalah. These games differ in some aspects but for my question it’s only important to know that the games could differ in the following: