Coding (from Fraktal SAS Programming): Unterschied zwischen den Versionen
K |
K |
||
| Zeile 11: | Zeile 11: | ||
When program coding starts most programmers make a very personal but tremendously important decision. If not advised otherwise, an individual coding an algorithm or data processing workflow, in whatever language, will go for either '''''private efficiency''''' or '''''collaborative transparency.''''' Both alternatives may be as well appropriate in one working context and lead to extremely high cost in others. In this course we will refer to the results of this decision as ''"Implicit Coding"'' vs. ''"Explicit Coding"''. | When program coding starts most programmers make a very personal but tremendously important decision. If not advised otherwise, an individual coding an algorithm or data processing workflow, in whatever language, will go for either '''''private efficiency''''' or '''''collaborative transparency.''''' Both alternatives may be as well appropriate in one working context and lead to extremely high cost in others. In this course we will refer to the results of this decision as ''"Implicit Coding"'' vs. ''"Explicit Coding"''. | ||
| − | * [[Implicit Coding (from Fraktal SAS Programming|'''Implicit Coding''']] | + | * [[Implicit Coding (from Fraktal SAS Programming)|'''Implicit Coding''']] |
| − | * [[Explicit Coding (from Fraktal SAS Programming|'''Explicit Coding''']] | + | * [[Explicit Coding (from Fraktal SAS Programming)|'''Explicit Coding''']] |
It is important to state here that this distincition, whilest of some relevance, is not a predicate indicating the value of or justifying the budget for a specific programmer's work. Nevertheless, the decision between implicit vs. explicit coding needs to be done on a team lead or project responsible level, aware of possible consequences and agreed to as binding for all participants, e.g. team members, in a specific context. | It is important to state here that this distincition, whilest of some relevance, is not a predicate indicating the value of or justifying the budget for a specific programmer's work. Nevertheless, the decision between implicit vs. explicit coding needs to be done on a team lead or project responsible level, aware of possible consequences and agreed to as binding for all participants, e.g. team members, in a specific context. | ||
Aktuelle Version vom 14. Mai 2014, 12:45 Uhr
|
|
|
|
When program coding starts most programmers make a very personal but tremendously important decision. If not advised otherwise, an individual coding an algorithm or data processing workflow, in whatever language, will go for either private efficiency or collaborative transparency. Both alternatives may be as well appropriate in one working context and lead to extremely high cost in others. In this course we will refer to the results of this decision as "Implicit Coding" vs. "Explicit Coding".
It is important to state here that this distincition, whilest of some relevance, is not a predicate indicating the value of or justifying the budget for a specific programmer's work. Nevertheless, the decision between implicit vs. explicit coding needs to be done on a team lead or project responsible level, aware of possible consequences and agreed to as binding for all participants, e.g. team members, in a specific context.
An inappropriate decision at this point may negatively affect product quality or overall cost.
Mixing both approaches is strongly not recommended.
|
|
|
|
