Timeline for Coping with an unfixable endless project
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2011 at 16:51 | comment | added | user23157 | I take your point; a shop that is well organised generally writes fairly decent, sane code. Those that aren't don't. The details are fairly by-the-by. | |
| May 20, 2011 at 20:29 | comment | added | David Thornley | @B Tyler: In practice the FS will quickly become obsolete. That's my experience and observations, anyway. This leads me to think that a shop that actually does maintain the FS is not going to be in this sort of mess anyway. So, while I think your advice is good, I also think it's de facto mostly useless. | |
| May 20, 2011 at 15:41 | comment | added | Jim G. | @B Tyler: ...In my experience not knowing what is being developed is the seed of mismanagement. - 100% agree. We just disagree on the remedy. | |
| May 20, 2011 at 14:49 | comment | added | user23157 | I take your point, but in my experience not knowing what is being developed is the seed of mismanagement. | |
| May 20, 2011 at 14:18 | comment | added | maple_shaft♦ | You both make valid points. Strong functional requirements are necessary for a solid testing practices, however when the project is already being mismanaged then this will help very little. | |
| May 20, 2011 at 13:58 | comment | added | user23157 | "that will quickly become obsolete" is the biggest fallacy in the whole of software management. If they become obsolete then update the FS so that they aren't. If you don't have a proper FS how on earth do you know what tests to write or if your software actually does what it want. For me this is everything (and there is a lot) wrong with agile: let's just start writing code, the tests are everything. Documentation is a waste of time, getting things clear and explicit is a waste of time... | |
| May 20, 2011 at 13:30 | comment | added | Jim G. | -1: Write clear functional specifications; pedantically - I strongly disagree because time and energy spent writing "pedantic, functional specifications" (that will quickly become obsolete) is time and energy that you can't spend writing functional unit tests that validate the code every automated build cycle. | |
| May 20, 2011 at 12:23 | history | answered | user23157 | CC BY-SA 3.0 |