Timeline for How can dev teams prevent slow performance in consumer apps?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 29, 2011 at 13:55 | comment | added | David Thornley | @user16764: There is often too little attention paid to giving developers test environments that are different from their development environment. My wife had a very hard time getting both an admin account (to develop in) and a more limited account (for testing), and before that had constant problems with accidentally putting something in a maintenance fix that wouldn't run on an ordinary user account. | |
| Sep 29, 2011 at 13:44 | comment | added | David Thornley | @Jerry Coffin: If all the developers here found ways to write code so it built faster, over several months there'd be very little change. It would take a good deal of effort to refactor on that scale, effort that would provide neither more user support nor more useful features. Moreover, I don't know how fast this particular codebase can be made to compile. It's already fairly modular. | |
| Sep 29, 2011 at 4:54 | history | made wiki | Post Made Community Wiki by geoffjentry | ||
| Sep 28, 2011 at 21:13 | comment | added | Jerry Coffin | @DavidThornley: IME, the same largely applies there. Build times will go up until it becomes a problem, at which point many developers suddenly find ways to write the code so it builds faster. The resulting code is usually better designed and more modular. | |
| Sep 28, 2011 at 21:12 | comment | added | Falcon | @user16764: That's how we did it lately. Worked great. | |
| Sep 28, 2011 at 21:00 | comment | added | user16764 | This was suggested in a Slashdot comment (about something) years back. The response was: "developers should develop on fast machines and test on slow ones." | |
| Sep 28, 2011 at 20:53 | comment | added | Loki Astari | Half the problem is that it is hard to test on a dev machine. Dev machines tend to be big and fast so a dev may never see the issue. Its hard to fix something if you can't see measure (be affected by) the problem let alone how your fix will change the behavior. | |
| Sep 28, 2011 at 20:43 | comment | added | David Thornley | In which case the company should buy me a decent sword, because I'm going to spend most of my time compiling. | |
| Sep 28, 2011 at 20:41 | comment | added | Crashworks | It's easy to fall into the trap of obsessing over things that don't matter, but if a cellphone ships with a UI so slow that incoming calls go to voicemail before the "Answer" button responds, clearly someone failed to improve performance when it did matter. | |
| Sep 28, 2011 at 20:37 | history | answered | Jerry Coffin | CC BY-SA 3.0 |