False dichotomy.
Which false dichotomy is that? The art-versus-craft one, that's what.
Most people (I'm not one of them, mind) would tell you that, for example, oil painting lies on the art side of the split, while programming (by whatever name you give it) lies on the craft side of the split.
Some people attack the dilemma by denying that programming is craft. Cobblers. Or, rather, not cobblers, but a totally inadequate response.
The truth is that the split is an illusion. In the ancient world, it certainly was. Our very word for what we produce, "technology", has at its heart an ancient Greek word, transcribed in the Latin alphabet as "techne" or "tekhne", that meant nothing more than "art".
So of course what I do is craft, and it is also art, because they are one and the same. Whether we call the craft craft, or engineering, or whatever, it is still art.
So I am an artist, and damned proud of it, just as I am a craftsman. The oil-painter's problem is that he has a blank canvas and racks full of paints, brushes, and so on, and someone wants a painting. My problem is that I have editors and compilers, linkers and debuggers, and someone wants a program. Progressing from the one to the other is applying at the same time of the art and the craft either of painting (the painter) or programming (me).
But the graphic designer also produces art, and craft.
Because, remember, the two things are one and the same. If you call the one a "creative" and the other a "developer" you are missing the point.
Your opinion may vary, but if it does, you are wrong.