4 ms·
1. Make it compile 2. Make it run 3. Make it work 4. Make it robust - Correct the errors 5. Make it failsafe - Handle the edge cases (out of memory, disk fu
by ryandrake 9y ago
1. Make it compile
2. Make it run
3. Make it work
4. Make it robust - Correct the errors
5. Make it failsafe - Handle the edge cases (out of memory, disk full)
6. Make it fast
7. Make it small
8. Make it clean (warnings, lint, beautify/style, clean up dead/commented code, in other words, polish the back of the cabinet)
I've met programmers in school who stop at #1 or #2. Most programming jobs get bogged down endlessly trying to get through the #4 backlog until the deadline comes along and they have to ship. Most developers, when asked to provide an effort estimate for a particular task only budget for #1, #2, and #3 (and with experience will learn to account for #4).