Most solutioning is art, given that you should have more than one way to reach the target state and target state itself is negotiable and non-concrete. When there are multiple options you are forced to analyze between them, sometimes you have a preferred option if the analysis has been done before. Your choices while solutioning will reflect your experience and how you think. In short, it definitely reflects 'you'.

You make similar kind of choices while programming as well. Hence, programming is definitely an art since there are many ways something can be implemented, almost to the level that you can recognize who has written the code by seeing the code itself. Most such programmers don't even have the visibility to higher level goals of the org they are working in, I used to be in this group earlier.

I remember it used to be a 'problem' for a lot of senior developers, who used to ask for consistency in how code is written, like spacing between keywords, indentation, start/end of parenthesis, naming convention, etc. Wondering if they'll settle for more 'Soul' in the code now :). Or maybe, they have permanently shifted to the other groups now - where only the output matters.