Is it good to have an interface plenty of methods which belong to different concepts, just to preserve the Liskov’s Principle?
I’m currently studying a course based on Software Design and I had a discussion in class with my professor and some classmates about a problem represented by the next scenario:
Creating an interface of interfaces
Background:
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.
Is this a Single Responsibility Principle violation?
I’m designing an OO graph library and at the moment I’m trying to figure out the design for a GraphEdge class. I’ve added setters and getters for it’s nodes, direction and weight. This seemes perfectly reasonable.
Is this a Single Responsibility Principle violation?
I’m designing an OO graph library and at the moment I’m trying to figure out the design for a GraphEdge class. I’ve added setters and getters for it’s nodes, direction and weight. This seemes perfectly reasonable.
Is this a Single Responsibility Principle violation?
I’m designing an OO graph library and at the moment I’m trying to figure out the design for a GraphEdge class. I’ve added setters and getters for it’s nodes, direction and weight. This seemes perfectly reasonable.
Is this a Single Responsibility Principle violation?
I’m designing an OO graph library and at the moment I’m trying to figure out the design for a GraphEdge class. I’ve added setters and getters for it’s nodes, direction and weight. This seemes perfectly reasonable.
Is this a Single Responsibility Principle violation?
I’m designing an OO graph library and at the moment I’m trying to figure out the design for a GraphEdge class. I’ve added setters and getters for it’s nodes, direction and weight. This seemes perfectly reasonable.
Is this a Single Responsibility Principle violation?
I’m designing an OO graph library and at the moment I’m trying to figure out the design for a GraphEdge class. I’ve added setters and getters for it’s nodes, direction and weight. This seemes perfectly reasonable.
SOLID Principles and code structure
At a recent job interview, I couldn’t answer a question about SOLID — beyond providing the basic meaning of the various principles. It really bugs me. I have done a couple of days worth of digging around and have yet to come up with a satisfactory summary.