Is this a feature envy smell?
In my Application, I wanted to seperate GUI and business logic with some kind of ModelViewPresenter-Design.
Is this a feature envy smell?
In my Application, I wanted to seperate GUI and business logic with some kind of ModelViewPresenter-Design.
Is this a feature envy smell?
In my Application, I wanted to seperate GUI and business logic with some kind of ModelViewPresenter-Design.
Is this a feature envy smell?
In my Application, I wanted to seperate GUI and business logic with some kind of ModelViewPresenter-Design.
Is it not direct usage of primitive pointer types form of Primitive Obsession?
Using primitive data types to represent domain ideas is code smell called Primitive Obsession. For example using string data type to represent human name – it is recomended to avoid this by defining domain specific value object with apropriate methods.
Is it not direct usage of primitive pointer types form of Primitive Obsession?
Using primitive data types to represent domain ideas is code smell called Primitive Obsession. For example using string data type to represent human name – it is recomended to avoid this by defining domain specific value object with apropriate methods.
Should the method describe its side effects? [duplicate]
N7: Names Should Describe Side-Effects
Names should describe everything that a function, variable, or class is or does.
Don’t hide side effects with a name. Don’t use a simple verb to describe a function that does more than just that simple action. For example, consider this code from TestNG:
Should the method describe its side effects? [duplicate]
N7: Names Should Describe Side-Effects
Names should describe everything that a function, variable, or class is or does.
Don’t hide side effects with a name. Don’t use a simple verb to describe a function that does more than just that simple action. For example, consider this code from TestNG:
Should the method describe its side effects? [duplicate]
N7: Names Should Describe Side-Effects
Names should describe everything that a function, variable, or class is or does.
Don’t hide side effects with a name. Don’t use a simple verb to describe a function that does more than just that simple action. For example, consider this code from TestNG:
Should the method describe its side effects? [duplicate]
N7: Names Should Describe Side-Effects
Names should describe everything that a function, variable, or class is or does.
Don’t hide side effects with a name. Don’t use a simple verb to describe a function that does more than just that simple action. For example, consider this code from TestNG: