craftsperson

Popularity of a technique or tool can definitely matter to a craftsperson, as they directly impact the availability and cost, as well as the marketability of that craftsperson's skills.

You: craftsperson who cares about what you produce, experiened with MV* JS apps, play well with others.

With social skills, as with any other discipline, merely following rules will make you a craftsperson, not an artist.

The craftsperson can be judged on their past works, and they can accurately judge the cost to do it again.

That's a hard thing for people with an aesthetic or craftsperson mentality to accept.

A tool in the hands of a well trained craftsperson is always better used.

Being a highly skilled craftsperson creating software for those who can't or don't want to is a very psychologically positive self identification.

As if there is some dishonor for being a dedicated and skilled craftsperson.

So, let the craftsperson choose what works best for his or her work.

Getting that done custom by a craftsman (craftsperson?) here in the US would probably cost a multiple of at least 2x and perhaps 5x.

I do it every now and again but for a craftsperson I don't feel that it is the ideal approach.

A craftsperson can make the most beautiful, elegantly designed thing that is a joy to look at, use, and serves as a conversation piece...

It's tempting to suggest to use "crafter", but that term has its own connotations different from "craftsman/craftswoman/craftsperson".

If someone doesn't want to work for your company because you used the word "craftsman" instead of "craftsperson", then it sounds like you just dodged a bullet.

I think the business of software engineering has changed in ways that make it much less amenable to the "craftsperson ethos".

When we use the term "craftsman" or "craftsperson" we have a very definite concept in mind, and it is nothing like "crafter." > [person #2:] Crafter, hmmmm.