Computer code is not art. It has no aesthetic quality. It’s generally not even seen and frequently hidden.
It’s engineering - you don’t need to get all up yourself by claiming to be “artists”.
Where this falls flat for me is, opportunities to write code that people will be willing to experience directly are rare. Much of it doesn’t even allow them to do so, or at least programmatically crams it all together in an unintelligible mess (ie. the javascript rendering a typical website). How can something be art if the audience is kept away from it? But even when it’s like that, people will still do it without a financial motive. You can still have a result in mind and go through the process of finding the shortest path to it, and that can still be art, even if some of the materials aren’t. Even if it’s not art, it’s exercising power, it’s desirable regardless of money.
That said, I do think there is something really special about code as writing, where it is written to be read and understood and making full use of it necessarily entails doing so. Shared awareness of abstract structures is really underrated.
Regarding the last paragraph:
If you’re thinking without writing, you only think you’re thinking. -Leslie Lamport
Regarding the rest:
It seems like he’s really only arguing that some programming is art. I’d argue that nearly all programming is art. And that all art is political. Therefore, nearly all programming is a political act.
I think that framing does a better job of explaining why some devs are not merely indifferent to AI coding but view it as a threat to the future of computing. But the author seems to be pro-AI, so I don’t think he can really put himself in that headspace.
Edit:
I was just reflecting on how exactly programming is an art form, and I related it back to the way I usually explain how games are art.
In a game, unlike in a book or a movie, you don’t just witness what’s “supposed to happen” — you can personally interject and ask “what if this happened instead?” By offering you the ability to actively inspect the game’s world from any angle you choose, it can create a deeper sense of the shape of the elements and themes of the game.
Code is similar. Any non-trivial chunk of code invites dozens of “what if?” questions, and the way the author chooses to handle each of those scenarios expresses some kind of philosophy about how the world should be. (Not just what the code currently does, but how it encourages or discourages certain kinds of edits.) These scenarios often have mutually-exclusive options, so it’s not possible to do the “proper” thing in all conditions. Trade-offs are inevitable, and so the code becomes a window to the values of the coder.
I think that part right there is why there’s such a gap between open source sentiments toward AI and enterprise adoption of AI. For FOSS code, the esoteric behavior of the edge cases of a subsystem’s subsystem is not a chore but a moral test.
In a megacorp though? The answer the corp wants is “whatever everyone else does”, or “whatever maximizes revenue”, or “whatever minimizes liability”. You kinda know the morality of the biz before you even consider the specific question. It’s not surprising, it’s not interesting, and delegating to a chatbot whose morals run on autotune doesn’t change much.
It is still art, and it is still political… but it’s Walmart home decor aisle art, and the politics of a Coke ad.
I honestly think trying to define programming as art is just an attempt to unnecessarily elevate it. Programming is utilitarian. It is meant for a specific practical purpose. It does not reveal a shared human experience the way a movie, book, or game does. I have no need to convince myself, a professional software engineer of this because I am perfectly happy accepting that what I do is useful and do not need to try to put myself in a category with artists.
All the author is saying is that people enjoy programming. I also enjoy eating. Is that an art? I even have my own “eating style” in that I like to eat food in specific order, combine two items into one bite, the way I build a bite, etc. But I’d never try to elevate it because I’m a normal person who doesn’t waste brainpower trying to make myself feel special.
I won’t begrudge anyone their definition of art, because it’s an extremely slippery concept.
But I do think it’s worth pointing out that there are clearly at least two rather different notions of art: one as a product with value that rich people like to buy and trade, and one as a behavior that all human beings perform. I don’t think the latter category has any inherent “elevation” to it, the way the former does.
And also that having a utilitarian specific practical purpose doesn’t automatically prohibit it from being art, in most popular conceptions of the term. Some of the earliest artifacts that are widely considered art were primarily utilitarian: cups, bowls, and other tools.
Also, a good excuse to share this excellent piece: Tomatoes, or How Not To Define “Art”
I certainly don’t disagree with the points made in the video. It in fact points out something related to what I’m saying. He states he notices that people that claim something is not art are often gatekeeping something from becoming “elevated.” I’m extending the converse argument: many people trying to claim something is art are trying to elevate it to a new status.
My problem with calling programming art is not that I don’t think programming is art, but rather that I think that label is not useful in this context. Programming is something that is very much valued without that label. Thus adding the label is just an attempt to tack on unneeded elevation to the craft. In some ways the video supports my viewpoint. The debate over what is art is a bit tired. It’s worth having, but personally I don’t think it is needed in this case.
I’m going to be real, “Ok, I think it is art, I just don’t want it to be called art” is a wild stance is any other context. As an extension of that claim, I’ll say it is bogus in this context too.
I didn’t say I think it’s art. I don’t know if it is, and I don’t really care if it is or not. I also don’t care if it’s called art. I’m just saying the mental gymnastics of trying to convince someone that something like programming as art is cringe.
If you’re defining programming as simply translating an algorithm. Into code as is, sure it isn’t art. However, designing abstractions and the structure which allows said algorithm to work with various parts of a program seamlessly and beautifully can be art.
Some people’s code is art (just not mine or yours I guess)
Have you ever looked at code and thought “oh this is beautiful”? Or - even better - have had someone else look at your code and say it? Pure bliss.
If I asked an AI to write a text on the topic “Programming is art”, that thought process wouldn’t happen. I wouldn’t experience the same emotions that come with writing it myself. For me, writing is art that I pursue regardless of money. I think people who enjoy writing code feel the same way.
Huh. The turnaround given the top comment here is interesting.
the Devil whispered behind the leaves, “It’s pretty, but is it Art?”
The Conundrum Of The Workshops by Rudyard Kipling





