I think the author misused the word "software development craftsmanship". Or he/she is not talking about THE software development craftsmanship as http://manifesto.softwarecraftsmanship.org/
It basically seems to just be a short list of tautologies. No one in their right mind would disagree on what is on the list, but they leave off basically anything about software that might actually help you achieve anything or improve the way you do it.
It seems to be some zen-like meditation based method of improvement, completely devoid of substance.