If an entity is composed, is it still a god object?
I am working on a system to configure hardware. Unfortunately, there is tons of variety in the hardware, which means there’s a wide variety of capabilities and configurations depending on what specific hardware the software connects to.
If an entity is composed, is it still a god object?
I am working on a system to configure hardware. Unfortunately, there is tons of variety in the hardware, which means there’s a wide variety of capabilities and configurations depending on what specific hardware the software connects to.
If an entity is composed, is it still a god object?
I am working on a system to configure hardware. Unfortunately, there is tons of variety in the hardware, which means there’s a wide variety of capabilities and configurations depending on what specific hardware the software connects to.
Inheritance in test classes
I have an interface Serializer with methods serialize and isSerializerFor. I created a first implementation of this using TDD, and ended up with a nice clean test case fully covering a nice clean implementation. To get a more concrete idea, here is one relevant commit.
Inheritance in test classes
I have an interface Serializer with methods serialize and isSerializerFor. I created a first implementation of this using TDD, and ended up with a nice clean test case fully covering a nice clean implementation. To get a more concrete idea, here is one relevant commit.
How to use the Decorator pattern to add little functionality to big objects?
This question regards the usage of the Decorator pattern to add little functionality to objects of large classes.
Alternatives to inheritance on complex structures?
I’m working on an ASP.NET Webforms project, using the MVP Pattern (which the presenters as you may know use a Page Controller pattern). I’m given a rather complex inheritance chain for my controllers. Below I depict a small example of the structure I’m facing (it is way bigger structure in my app):
Alternatives to inheritance on complex structures?
I’m working on an ASP.NET Webforms project, using the MVP Pattern (which the presenters as you may know use a Page Controller pattern). I’m given a rather complex inheritance chain for my controllers. Below I depict a small example of the structure I’m facing (it is way bigger structure in my app):
Inheritance vs ‘specification’ by fields
I’m currently reading ‘Head first design patterns’ and I already have a few questions on the first chapter of the book.
This chapter introduces the ‘prefer composition over inheritance’ design principle, by explaining the ‘Strategy-Pattern’. My question isn’t about the pattern, but rather about a more basic design decision in one of the examples:
Inheritance vs ‘specification’ by fields
I’m currently reading ‘Head first design patterns’ and I already have a few questions on the first chapter of the book.
This chapter introduces the ‘prefer composition over inheritance’ design principle, by explaining the ‘Strategy-Pattern’. My question isn’t about the pattern, but rather about a more basic design decision in one of the examples: