Timeline for Complexity point of no return. What do you call that?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5, 2011 at 15:29 | comment | added | Mark Booth | Snap! programmers.stackexchange.com/questions/68824/… *8') | |
| May 5, 2011 at 12:04 | comment | added | Thibault J | I'll go for the "technical bankruptcy" term, I like it. And I'll also use your definition. | |
| May 5, 2011 at 12:03 | vote | accept | Thibault J | ||
| May 5, 2011 at 11:43 | comment | added | mojuba | @ Developer Art: ...realizing if you're still happily before that time or sadly passed beyond it - I think that's the key in giving a good definition of the point: a project that's gone beyond the point is one that no engineer would take over voluntarily. | |
| May 5, 2011 at 10:31 | comment | added | user8685 | @Thibault J: I do not believe there is a specific term for that moment. It's more about realizing if you're still happily before that time or sadly passed beyond it. | |
| May 5, 2011 at 9:43 | comment | added | Jaap | I like your term 'technical bankruptcy'. It suggests that just like in a real bankruptcy, you have to look carefully which parts are salvageable and which should be left behind. And maybe some debt restructuring is all that's really needed :) | |
| May 5, 2011 at 9:33 | comment | added | Thibault J | Thank for your answer. I'm aware of the concept of "technical dept". Every project have some kind of technical debt. What I mean is : how do you call the moment where this debt become so hight that you would prefer throwing the project to garbage and start again? | |
| May 5, 2011 at 9:12 | history | answered | user8685 | CC BY-SA 3.0 |