Timeline for Good way to program an orchestration / processflow
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 7, 2015 at 10:34 | vote | accept | Michel | ||
| May 29, 2015 at 10:34 | comment | added | Michel | I really like your update. It provides me with a lot of info why other methods (which we might think of) are not the best idea. | |
| May 29, 2015 at 9:36 | comment | added | Ewan | No I wouldn't recommend it for 'normal' things, just where you have been told the exact logic rather than the required results, or have some logic which needs to be defined by users. if you see what i mean | |
| May 29, 2015 at 9:32 | history | edited | Ewan | CC BY-SA 3.0 |
added 1231 characters in body
|
| May 28, 2015 at 20:03 | comment | added | Michel |
All the patterns-, TDD-, unit test etc. books never seem to cover these kind of problems imho, and I can't relate this 'big if block' to the clean Calculator.Add() clean code....
|
|
| May 28, 2015 at 20:02 | comment | added | Michel | Also the code seems so 'procedural', which also seems to be a bad habit. | |
| May 28, 2015 at 20:01 | comment | added | Michel | I definately agree with 'it will be easy to read and easy to change'. But nowadays it seems almost like a crime to put more than one 'if' in a method. | |
| May 28, 2015 at 15:46 | history | answered | Ewan | CC BY-SA 3.0 |