in my opinion, the issue is not at its root about being a good craftsman.

what ultimately matters to me is avoiding the painful/frustrating/stressful productivity crash that can occur when maintaining software.

software craftsmanship is a means to that end.

this is essentially in agreement with what the article said. i think its worth clarifying that there are things you are trying to avoid, and then certain practices are means to that end.