Software Craftsmanship

Software Craftsmanship: While sounding really nice at first glance, I really don't see where to draw the boundary between a software craftsman and anyone else working in the industry. Of course the things listed in the Software Craftsmanship Manifesto ("Not only X, but also Y.") are all good things (tm). However, improving on one thing always comes at the price of getting worse at something else. So at what cost does it come? I like the wording of the Agile manifesto much more ("We value X over Y."). I'm not surprised that the whole Software Craftsmanship idea is so vague and romaticized.