re: “There is no objective way to know if software is done, we need the backing of a community to know when it has achieved its goals.” – It has been my experience that the “community” consists of both users and developers; users in that the software meets their needs, and developers in that the software meets their needs as well.

Best,
Eric

There will ALWAYS be a better one. We learn by doing ang coping and doing it better This is good, how else should this evolve? =)
And it keeps up the challange.

This is a good introduction. I agree, the role of Code Reviews is a key aspect to the process. There is no objective way to know if software is done, we need the backing of a community to know when it has achieved its goals.

Best,
al

If the design meets the three criterion mentioned above, especially scalability, it will easily lend itself to change, be it during implementation of the current requirements, maintenance of these features or the implementation of new feature sets.

Best,
Eric

The code needs to be open to change and refactored continuously as we advance toward final product, the good design becomes even better. No matter how good the initial design is, there is usually (always?) better one to be discovered in development phase

Cheers,
Adnan