I think I agree than programming can be a craft - I think of myself as a craftsman, and usually use the term "artisanship" to describe the quality of code. I do

I think I agree than programming can be a craft - I think of myself as a craftsman, and usually use the term "artisanship" to describe the quality of code. I don't think that it's necessarily a craft, though. Most academic code that I've worked with is not written in a way that I would consider up to my standards, but it gets the job done and is often targeted at expanding human knowledge. In that way, programming can be seen as more like physics or other 'hard sciences'. Come to think of it, Photoshop is the same way. If I'm editing a headshot for a pageant contestant (which I've done quite a bit in the past), that's firmly in the "craft" side of things. If I'm putting together a UX design for a webapp, what's a bit ambiguous - there are design elements that are "craft-like" and there are usability considerations that are "science-like". If I'm writing a droplet to do batch processing of a whole series of photos I've take on a shoot and have to test that it's doing what I need it to do over a wide variety of inputs... well, we're back in the "science-like" side of things again. In fact, I would argue that the toolset and even the discipline are almost irrelevant in this discussion. "Craft" versus "science" is a matter of process and mindset more than anything.