Maybe the name (“software craftsman”) is not that important, but what it stands for, at least in my view, does. In the craftsmen manifesto tdd is not mentioned. But in the book “The Software Craftsman: Professionalism, Pragmatism, Pride” you can find paragraphs on f.e. “How Do I Convince My Team to Do TDD?”. Do a “software craftsman advanced” course and you get “Best practices: using testing and test driven development […]” Clean Code: Software Craftsman Advanced Instructor-Led Training Course | ProTech.
Uncle Bob, writer of the clean coder and long time proponent of tdd just said
https://twitter.com/unclebobmartin/status/1030819434510745601
The disagreement is left implicit which makes this a strange read, but to me his view (see complete tweet) is new. In the past he said quite something else, f.e. in the clean coder book. Something like “if you do not practise tdd you’re unprofessional”. Opinions like these still sing around. Some employers demand you keep singing this song with them.
Dan North made some valuable remarks on software craftmanship btw:
Software Craftsmanship risks putting the software at the centre rather than the benefit
the software is supposed to deliver, mostly because we are romantics with big egos.
https://dannorth.net/2011/01/11/programming-is-not-a-craft/comment-page-1/
