>Apply the same question to music, or drawing

Why asking outside the technical domain? Code is instructions for a machine for it to do a task. All this philosophy around code as art or whatever it's in my opinion just intellectual onanism, looking at the screen and thinking "damn I'm the shit just look at that oneliner oh my gawd, look at those perfectly applied GoF patterns. Pure engineering. Poetry is code".

The craft you say. What's the intent of it? Having code that's nice to look at and/or understand or the product of such code execution? For the later coding "as craft" is irrelevant. I've seen beautiful and mind blowing software with horrendous code, an entire company working as a clock with a 4 millions LOC single php file, the most cringe inducing spaghetti code I've ever seen. Users don't care. The software works as expected, fast, almost no bugs after >10 years of development. It's purpose fulfilled. And I've seen perfect code running slow as fuck.

I've done manual and CNC machining. I forgot the last time I wrote G codes in the thousands LOC. Everything now is CAD CAM. A software wrote the code for me, I just designed the thing. Same with 3D printing. Should I write the code myself to respect the craft? Of course not, that would an incredible waste of time. I want the physical piece in my hand or an application running fast and without crashing. Why would I care for HOW the code is written?

Exactly, well said.

I think folks in the craft need to mature a bit and understand this very well.