Timeline for I've inherited 200K lines of spaghetti code -- what now?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 6, 2012 at 19:33 | comment | added | Lorand Kedves | @Bill: I think you say exactly the same as I have written about the content and creation of that documentation... ;-) | |
| Jul 6, 2012 at 12:05 | comment | added | BillRobertson42 | Of course they don't know what they want, that's the "work it out" part, which is different than just picking something like documentation and patterns and saying do these things. Those things are good things, but it has to be a process that involves the group, and if you start off with things that they don't see value in first you will have a difficult time getting buy in. -- Cheers! | |
| Jul 6, 2012 at 9:04 | comment | added | Lorand Kedves | @bill: The question says "there is not a consensus of opinion about what is needed for the path ahead". They don't know! I assume there are serious debates without real insights on the system that must be saved "somehow". A programmer's task in this situation is obvious (at least to me): give a correct analysis from the technical point of view to help making a rational decision. | |
| Jul 6, 2012 at 5:49 | history | made wiki | Post Made Community Wiki by Conrad Poelman | ||
| Jul 6, 2012 at 1:21 | comment | added | BillRobertson42 | I agree that step #1 is to work out what they want from you, but the next step should be to do that, and if the next step is not to document the state of affairs then don't do that too much. If you do they won't appreciate it. | |
| Jul 4, 2012 at 5:11 | history | answered | Lorand Kedves | CC BY-SA 3.0 |