1) bug free - well tested for all foreseeable problems
2) efficient - it should be fast and not hog memory
3) robust - it should be able to handle unforeseen events
4) maintainable - the next person to see it shouldn't have a problem fixing it or adding to it.
2007-03-09 03:23:38
·
answer #1
·
answered by bytekhan 2
·
0⤊
0⤋
First and foremost, meet the requirements. After that, you want no memory leaks, but if you are dealing with leaky third-party software, then you'll want to mitigate the leak that you can't plug, most likely through software rejuvenation. Then you'll want your software to follow whatever pattern the entire project is following (message pipes, objects, modular components). You'll want to test the cooties out of your code and try to break it, and then fix resulting problems. And lastly, make it understandable by other humans so your code can be maintained.
2007-03-09 12:32:26
·
answer #2
·
answered by icnintel 4
·
0⤊
0⤋
Satisfy my the development leader. Everything else is BS. If they are happy with you, you will be happy. If you try to make things your way instead of their's, you'll be in trouble. The project managers are a different breed of a**-holes.
PS~ I don't mix work with pleasure. Most of the time my job is not about satisfying myself lol
2007-03-09 11:55:46
·
answer #3
·
answered by Smutty 6
·
0⤊
0⤋
User-friendliness, efficiency, usefulness
2007-03-09 14:14:02
·
answer #4
·
answered by fjpoblam 7
·
0⤊
0⤋