Return to Answer

Quick Answer: Use your approach if it makes your software work. However, look after repeating blocks of code, because you may want to move them to common class (or business layer) later on. Thus will ensure that you are constantly refactoring and refining your code.

In this situation, i try to stick with principles of KISS and YAGNI - meaning, "Keep It Simple Stupid" and "You Ain't Gonna Need It".

Quick Answer: Use your approach if it makes your software work. However, look after repeating blocks of code, because you may want to move them to common class (or business layer) later on. Thus will ensure that you are constantly refactoring and refining your code.

In this situation, i try to stick with principles of KISS and YAGNI - meaning, "Keep It Simple Stupid" and "You Ain't Gonna Need It".

KISS - would refers to keeping your code with simple constructs and easy to understand, more simpler your code, easier to maintain it is in long run. YAGNI - refers to principle in keeping your code out off over-engineering with unnecessary chunk of codes, that you think will be used in future development.

Quick Answer: Use your approach if it makes your software work. However, look after repeating blocks of code, because you may want to move them to common class (or business layer) later on. Thus will ensure that you are constantly refactoring and refining your code.

In this situation, i try to stick with principles of KISS and YAGNI.

Quick Answer: Use your approach if it makes your software work. However, look after repeating blocks of code, because you may want to move them to common class (or business layer) later on. Thus will ensure that you are constantly refactoring and refining your code.

In this situation, i try to stick with principles of KISS and YAGNI - meaning, "Keep It Simple Stupid" and "You Ain't Gonna Need It".

Quick Answer: Use your approach if it makes your model work. However, look after repeating blocks of code closely, because you may want to move them to common class (or business layer) later on. Thus will ensure that you are constantly refactoring and refining your code.

In this situations , personally i try to stick with principles of KISS and YAGNI.

Quick Answer: Use your approach if it makes your software work. However, look after repeating blocks of code, because you may want to move them to common class (or business layer) later on. Thus will ensure that you are constantly refactoring and refining your code.

In this situation, i try to stick with principles of KISS and YAGNI.