Manifesto for Software Craftsmanship

On AgileEE 2010 someone has mentioned Manifesto for Software Craftsmanship.
Here it is:

• Not only working software,
      but also well-crafted software
• Not only responding to change,
      but also steadily adding value
• Not only individuals and interactions,
      but also a community of professionals
• Not only customer collaboration,
      but also productive partnerships

That is, in pursuit of the items on the left we have found the items on the right to be indispensable.

See original version




I've never met this manifesto before and to tell the truth  I'm disappointed with it. It's clear that making a software in a right way is better than making it in a bad one. But the manifesto could be updated with absolutely any points, e.g. "Not only working software, but also software build on the right technologies". Or "Not only responding to change, but also not breaking a completed functionality".

In conclusion, there is not enough completeness for such a generalization.

--------------------------------------------------

На AgileEE 2010 был упомянут Manifesto for Software Craftsmanship, не помню уже кем.
Вот он: 

• Not only working software,
      but also well-crafted software
• Not only responding to change,
      but also steadily adding value
• Not only individuals and interactions,
      but also a community of professionals
• Not only customer collaboration,
      but also productive partnerships

That is, in pursuit of the items on the left we have found the items on the right to be indispensable.

Оригинал здесь

Раньше я с этим манифестом не сталкивался, и, признаться, я им разочарован. Понятно, что делать софт хорошо - лучше, чем делать его плохо. Но сюда можно было написать любые пункты, например: Not only working software, but also software build on the right technologies. Или Not only responding to change, but also not breaking a completed functionality.

В общем, не хватает полноты для такого высокоуровневого обобщения.