Timeline for Does profiling without benchmarking lead to micro-optimization?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2011 at 5:47 | comment | added | quant_dev | The project manager should gather the user requirements. | |
| May 9, 2011 at 2:10 | comment | added | Мסž | @rwong: at some point a user sits there and goes "this is slow". Ideally the manager makes it clear to the developer what the user will be looking for. | |
| May 9, 2011 at 1:00 | comment | added | rwong | The project manager probably only tells the developer that "You should measure this, this, and that." and leaves the details to the developers. How does the project manager find out whether the developer is doing it right or wrong, if it is up to the developer to determine whether the test scenarios and/or the test mechanism is realistic or not? (Is the average project manager usually more knowledgeable about the proper ways of performance testing than the average developer?) | |
| May 9, 2011 at 0:39 | history | answered | Apalala | CC BY-SA 3.0 |