The entire concept of art is relatively recent (from the Renaissance on), the ancient Greeks considered a sculptor to be a craftsman just like a smith or carpenter.
And the Renaissance artists had to make a living somehow, much of their art we know today was made to order for Church, State or rich merchants.
We may consider "pure art" to be "form without function" and "pure utility" to be "function without form". But fields like industrial design, architecture and engineering (ex. bridges) has room for both: Aesthetically pleasing form that merges well with their function.
If programming is art, it's the form+function sort of art. And just like with bridge building, the form part is optional - if the program works and the bridge does not collapse they are doing their job.
I don't consider the code for my day job to be art either. But I still think art can arise under such conditions, generally because someone with the power to do so goes beyond the call of duty and decides to make their bridge or code not only functional but beautiful as well.
There are plenty of constraints that can stop considerations of form dead in their tracks; like whether the client is willing to pay extra or wait longer for a more aesthetically pleasing result, or how much control you have over the final result - there are limits to how creative you can be if you are a subcontractor for a bridge pillar, or if you are designing an ad that needs to fit within the company's design guidelines and an existing ad series.
Still, I think art can arise in the most unexpected places, it's mostly a matter of spotting the opportunities and deciding that it is worth the bother.
And the Renaissance artists had to make a living somehow, much of their art we know today was made to order for Church, State or rich merchants.
We may consider "pure art" to be "form without function" and "pure utility" to be "function without form". But fields like industrial design, architecture and engineering (ex. bridges) has room for both: Aesthetically pleasing form that merges well with their function.
If programming is art, it's the form+function sort of art. And just like with bridge building, the form part is optional - if the program works and the bridge does not collapse they are doing their job.
I don't consider the code for my day job to be art either. But I still think art can arise under such conditions, generally because someone with the power to do so goes beyond the call of duty and decides to make their bridge or code not only functional but beautiful as well.
There are plenty of constraints that can stop considerations of form dead in their tracks; like whether the client is willing to pay extra or wait longer for a more aesthetically pleasing result, or how much control you have over the final result - there are limits to how creative you can be if you are a subcontractor for a bridge pillar, or if you are designing an ad that needs to fit within the company's design guidelines and an existing ad series.
Still, I think art can arise in the most unexpected places, it's mostly a matter of spotting the opportunities and deciding that it is worth the bother.