Timeline for Could taking design lightly be a pitfall of agile methodologies causing constant rework or is it a misunderstanding of the methodology?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2014 at 3:38 | comment | added | daaxix | Exactly my point. Not all problems work well with heavy agile/TDD solutions. | |
| Jun 28, 2014 at 6:57 | comment | added | BЈовић | I do not know python that well to read it, and say whether it is good or not. Anyway it also depends on the developer. Last thing : maybe TDD wasn't right solution for that problem. | |
| Jun 27, 2014 at 19:29 | comment | added | daaxix | @BЈовић, whatever the spin in the blog, TDD utterly failed at the proper implementation of a Sudoku solver, this is not how you write good software, go read Jeffries' TDD code... | |
| Jun 27, 2014 at 19:24 | history | edited | daaxix | CC BY-SA 3.0 |
added 397 characters in body
|
| Jun 27, 2014 at 19:16 | comment | added | daaxix | Waterfall is just as bad as extreme Agile...but I have never met anyone who does "waterfall." Most good engineers take a hybrid approach...like I said, some people take it too far, i.e. they drink too much of the Agile koolaid, I'm not saying it isn't useful at all, I'm saying you really do need design as well as iteration. | |
| Jun 27, 2014 at 8:05 | comment | added | BЈовић | You link at the end is total garbage, written by someone taking things out of context (at the end). Also, agile doesn't mean not doing design - it means not doing full design up front. Just to add : I have seen waterfall and v-model implementations done very poorly. | |
| Jun 27, 2014 at 7:44 | history | answered | daaxix | CC BY-SA 3.0 |