Timeline for How do you avoid endlessly iterating through equally sub-optimal designs?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 2, 2018 at 17:18 | comment | added | radarbob | OP, I see you stuck in the mechanics of code solution, so yeah you "might as well mark this answer." The best code we've written was after a very careful analysis of the requirements, derived requirements, class diagrams, class interactions, etc. Thank goodness we resisted all the heckling from the cheap seats (read management & co-workers): "You're spending too much time in design", "hurry up and get coding!", "that's too many classes!", etc. Once we got to it, coding was a joy - more than fun. Objectively that was the best code in the entire project. | |
| Mar 1, 2018 at 4:38 | vote | accept | Jonathan | ||
| Feb 28, 2018 at 16:44 | comment | added | Jonathan | Also I like how you broke it down into steps so there is some sort of loose procedure for assessing the situation. | |
| Feb 28, 2018 at 16:43 | comment | added | Jonathan | I might well mark this as the answer, this makes the most sense to me and there appears to be a consensus about simply reassessing the problem itself. | |
| Feb 28, 2018 at 16:02 | history | answered | cmaster - reinstate monica | CC BY-SA 3.0 |