OO Design: hint EntityManager to preload some datasets
say I have an EntityManager that can read(PK) a dataset from the DB and return it.
Term for a Class with Multiple Interfaces
Say I have a class that implements multiple interfaces. I pass the same instance around using a different interface, depending on what the consumer is interested in.
Is there any difference between interfaces and abstract classes that have abstract methods only?
Let’s say we have an abstract class and let this class has only abstract methods. Is this abstract class different from an interface that has same methods only?
Coarse grained remote interface vs encapsulating business logic
I’m writing a Web Service that will be consumed by a Mobile client.
The need for adding an interface to every class [duplicate]
This question already has answers here: What is the point of having every service class have an interface? [duplicate] (6 answers) Do I need to use an interface when only one class will ever implement it? (16 answers) Closed 11 years ago. My coworker and I are arguing very hard about this topic. He’s thinking […]
serving up future-proof kinfolk – extensible contract interfaces [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. Ok, I have this human here, but what […]
Violating the Interface Segregation Principle?
I currently have an interface named InternalEntityIdTransformer, which has a getInternalId method, that given an external id returns the corresponding internal one.
What did Rich Hickey mean when he said, “All that specificity [of interfaces/classes/types] kills your reuse!”
In Rich Hickey’s thought-provoking goto conference keynote “The Value of Values” at 29 minutes he’s talking about the overhead of a language like Java and makes a statement like, “All those interfaces kill your reuse.” What does he mean? Is that true?
Programming against a protocol in Objective-C
I stumbled accross the SOLID principles. There is one burning question. Should I always use protocols? I never saw someone using them in the way that a Java developer would use them.
Interfaces, Adapters, exposing business objects via WCF design
I know there have been countless discussions about this but I think this question is slightly different and may perhaps prompt a heated discussion (lets keep it friendly).