When something is brought into the world through human intention, it has the possibility of being art. A human must stand next to it and say "This is mine."
The human role in the creation of art is non-negotiable.
as of yet, there’s still no such thing as a print created entirely by a machine. Someone made the scan, prepared the print file, chose the paper stock, proofed the prints. Or at least some of those steps, depending on the print.
The point is, there’s no as a print that is 1:1 equivalent to an original painting. There are artistic choices embedded throughout the process that influence the result and make some prints “better” than others.
It’s easy to assume an image is just an image, a bunch of pixels with different numerical color values. But the real world has so much more detail than that.
IMO the original painting is art, a faithful copy is also lesser art, but a print is not art, because it takes significantly less skill and creativity to print thousands of it. It isn't worthless nor slop, though.
Basically, art speaks to our sensibilities, so we expect to find a message in there. LLMs can't create, only mix-and-match what exists in their training data set. You could slop a new painting, make a special canvas printer, and exhibit it in a blind test. Some people will think it's art because they find meaning in it, while others will think it's not art because they'll recognize several meanings slopped together in a nonsensical way.
In reality, it was never art, because the creator, a statistical algorithm, never had any message to convey in the first place.
I am a programmer who likes aesthetics. I think about how aesthetic it is to not have to deal with certain production incidents for certain blocks of code because the typelevel computation tells me it would be a compiler bug if it screwed up. I like the feeling of realizing those 100 LOC could just be 10.
I sometimes tell people of when I came down from Mt. Fuji, there were wispy clouds and grand nature below me, picturesque like a painting. At that time, I likened it to the beauty I felt when I was first learning Haskell. But I say it because I expect it to be a rare kind of sentiment.
The thing with art and music is that they are easy to appreciate, and the appreciation grows deeper with more consideration. I love reading the placards in museums and attempting to understand why the artist did what they did, I like it more than even looking at the piece itself.
Code (and math, for that matter) is almost the same except for one key difference: they are not easy to appreciate without deliberate training, training which is often far to the side of anything most people need/want to deal with.
> The thing with art and music is that they are easy to appreciate
I get what you mean (and agree w.r.t. math/code) but notably, I think appreciation for a lot of things still accumulates if you put in the work.
As an amateur violist, I can attest that I gained a totally new appreciation for most of the pieces I've studied and played in an orchestra in the past.
This not only includes "unknown" classical music from different eras, but also the obvious (popular) candidates like Beethoven's 6th, Dvořak's 9th and Grieg's "Peer Gynt" suites.
And there's a lot of great music one needs to get into first; for expample: I love Tool songs exactly for that, and there are certainly more obscure artists :)
So, I suspect the thing about maths and code is mainly just caused by the fact that people can go through life just fine without really interacting with them on the level required to develop the smallest bit of "taste" (as opposed to e.g. music).
> The thing with art and music is that they are easy to appreciate
> Code (and math, for that matter) is almost the same except for one key difference: they are not easy to appreciate without deliberate training, training which is often far to the side of anything most people need/want to deal with.
I would argue that this exists on a spectrum. There's lots of art and music that's pretty difficult to appreciate without deliberate training, and indeed there are whole categories of music which we would probably call music for musicians.
For example, the album Kind of Blue by Miles Davis is loved by many and is considered by most people to be the best gateway record into the world of jazz, because it's easy to listen to and appreciate. An album like Sketches of Spain, and especially an album like Bitches Brew, are more difficult for the average non-musician listener to get into.
An even more out-there example for music is Allan Holdsworth. In certain circles, he's a well-known and well-regarded name, considered highly influential. Most people have no idea who he is or what he did. (A bit like that cutaway in Family Guy where they jumped to Benjamin Disraeli and he simply said: "you don't even know who I am!").
Similarly, in art and painting, you often need training to understand why something was especially impressive. Now that we have photography, some old paintings can feel "boring" if you don't know how to appreciate the level of difficulty in producing a near-photorealistic work in the 1700s.
Conversely, some math is very easy to appreciate without training! I had a buddy who I got excited about math simply by explaining the Fibonacci sequence and the golden ratio, then showing trivial examples of how they appear in nature. My friend got lit up about math that day in a whole new way.
Coding is not really programming. It is certainly a highly adjacent skill, but coding is not the same as programming. To quote Leslie Lamport, coding is to programming as typing is to writing.
A collective of workers in a field can very much decide what they want to get payed for. Craftsmen did exactly that for centuries, and that's in fact what makes them being known for quality and is thus in fact their business moat.
Programming as an art form always reminds me of the Einstein quote; "Pure mathematics is, in its way, the poetry of logical ideas". Both are just art forms you cannot appreciate without some understanding of it. Arguably thats true of all art actually, its just that the more familiar forms, like painting or music, can be understood at a basic level without an understanding, whereas mathematics and programming are essentially alien to the casual observer.
Sure, some programming might be art. I've written programs that could qualify. But most isn't, unless you also want to count preparing a balance sheet for a corporation as art. Get over it.
I wish I could find the quote, I think it was on C2 Wiki, but alas, it was something like:
If you're an artist, programming is your clay, if you're an engineer, programming is your building material.
Point being, which I always connected with, was that programming is a medium for expressing a lot of things. Just like you can use paper and pen to write poetry or a dry technical manual. And everyone gets to decide how they see it and use it.
I am so fascinated about this angle -- whether programming is art or not. This is one of the things that got me to HN recently and I love reading these discussiong as a non-programmer.
While I love art, I am not an art historian or critic, so the definition I have for it is highly subjective -- in my opinion one of the functions of art is communication with other people (often through time and space). For art to fulfill its telos, so to speak, the message that it carries must also be read (heard, perceived) by somebody and then, if it's great art, eventually someone would want to respond to it.
The message can be simple, complex, subversive, stupid, clever, it can be an observation about world, a joke, a profound truth, a memory, a question, a snapshot, a curiosity, a trick, and a ton of other things. And sure, the message can be distorted, misunderstood, twisted, forgotten, lost, etc, but if no one "reads" it and no one "talks" to it, it might as well be glossolalia.
So my question for folks who do consider programming art -- do you "read" other people's code like this? Do you exchange ideas through code? Have you ever trolled great coders of the past through your code or tried to prove them wrong?
I hope my question doesn't come off as complete nonsense.
P.s. I know that there are programming manifestos which to me sounds like there is a layer of meaning that the code carries and this meaning goes beyond pure machine instructions or software functionality, but I'd love to read answers of actual programmers.
> So my question for folks who do consider programming art -- do you "read" other people's code like this? Do you exchange ideas through code? Have you ever trolled great coders of the past through your code or tried to prove them wrong?
Yes, 100% yes. I have always said that I reading someones code to me is akin to reading a personal diary or memoir. It exposes so many thing about their frame of mind and world view. I consider it beautiful and the advent of LLMs greatly muddying this signal (it has absolutely not REMOVED IT) has been incredible painful.
I strongly agree that programming is art, but I think there's a difference between other art forms.
A novel is both how it's made and what it is, and so is a piece of music.
Programming produces two different outputs: the code and the program. What users consume, and care about, is the program. The code may or may not be read by other programmers but it's not the main output. (It would be extremely weird to output code in a language that can't ever be run.)
And so I think the beauty or effectiveness of the program matters more than the beauty or elegance of the code. Those are not entirely orthogonal of course, but only loosely coupled.
A programmer should care a lot about the program, and a little less about the code. Vibe programming (where the programmer doesn't care one way or another) to me is a crime; but you can certainly use AI to code, and still care about the finished product, and make it good.
From a previous comment, vis-à-vis compilation vs. code generation:
> High-level programming languages use well-defined, limited syntax to encode program behavior in a deterministic way. Compilers translate these directions into programs that should have identical behavior between compiler runs and between different compilers. (If they don't, that's a compiler bug, or else an artifact of UB.) This means you can structurally and provably rely on the high-level programming layer without worrying about what's underneath: the assembly is abstracted away. You also get the massive benefit of being able to tweak and improve the assembly layer independently of the programming language layer, so long as the contract between language and compiler is not violated.
> If AI is a "layer of abstraction," so is working with a bunch of contractors to make your app. The definition is broadened to the point of absurdity. (Solely: "I don't have to think about code anymore," which only touches on the most superficial aspect of an abstraction.)
If there was a way to get a reproducible, deterministic mapping between natural language and code by way of a LLM, that would be an abstraction. But... that's just called a programming language (specifically a transpiler).
Programming is special in the sense that it is one of those direct experiences of mere language instructions being used to make things work - a form that resembles incantations and sorcery of the old times.
Of course there are many other indirect instances of language being used as the primary tool to move, but programming happens to be a direct raw unadulterated first hand experience into building things with nothing but raw language primitives.
Before AI, some programming could be considered be considered art. There are definitely codebases that are more beautiful than others. But now with introduction of AI you can’t consider any code as art as you have no idea who produced it. Yes, it may be looking good, but from that perspective it’s just randomly produced without the thought of being art. And at some point it will be refactored into oblivion by something that doesn’t care.
And I have much love for good frameworks and design.
I'm fortunate to have started gno.land before AI, yet just late enough to finish it with AI. The GnoVM (gno.land) is also art -- go interpreting go, but in a novel multiuser context, a re-imagining of TBL's WWW in Go and markdown. AI was used for final touch polishing. Couldn't have ended up any better.
AI is not yet there to grok the artistry of code. But it will eventually, and humanity will benefit from it necessarily, not because it is demanded, but because people like us desire it. Push forward.
Right on. And similarly, you don't need to learn farming to be able to cook good food, just like you didn't need to know assembly language or machine code to be able to write programs before AI.
I don't see it.
Programming CAN be used to generate art, but is not an art by itself.
I cannot imagine lines of code be exhibited in a museum. I can appreciate smart or witty solutions for a problem, but that is not what art is.
I can appreciate a quick solution for a Rubik cube, I can even see the Rubik cube itself in a museum, but I cannot imagine the steps or instructions for that quick solution in a museum (unless that paper has historical significance).
There are different kind of arts. There is the art of a craftsmen and there is beautiful art. The former is rarely exhibited in museums unless is also has an historic value. It's the kind of excellence with that you do your work and it can be in fact in every kind of work you do.
Being a humble rank-and-file programmer I did produce pieces of code that I will be proud forever as well, e.g. this snippet to control the length of $PWD in bash that I still use almost unchanged 25 years later:
# How many characters of the $PWD should be kept
local pwdmaxlen=30
# Indicator that there has been directory truncation:
#trunc_symbol="<"
local trunc_symbol="..."
if [ ${#PWD} -gt $pwdmaxlen ]
then
local pwdoffset=$(( ${#PWD} - $pwdmaxlen ))
newPWD="${trunc_symbol}${PWD:$pwdoffset:$pwdmaxlen}"
else
newPWD=${PWD}
fi
I agree, is the 100th rest api I’ve made for my 5th employer art? I don’t think so. It’s just a way to (maybe) make my employer money.
I’d say the brainfuck language on the other hand is art. Hard to draw a fine line as to which is which.
I can say most if not all the projects I’ve ever made land in the former. I’ve made some clever solutions but nothing approaching something with meaning.
There can be beauty in even the smallest of things. You can tell alot about a person by how they choose to structure even down to the loops and methods.
Writing by itself isn’t art, but poetry and literature are. And, by the same token, I don’t expect most works of literature to be exhibited in a museum — books are easily copied, so there’s little value to just having the book’s text in a museum.
Works like the Black Perl[0] are decidedly artistic in nature. Demos (in the demo scene sense) are an artistic endeavour. Competitions like the Obfuscated C Contest or the Underhanded C Contest are very much judged on aesthetics.
> I cannot imagine lines of code be exhibited in a museum.
Honestly, I can. The author of this article wrote Twisted. I certainly can imagine a museum where computer history is explained along with all the software achievements that made a huge impact on software engineering as a whole, and Twisted would have a place in it.
There's a 'joke' in engineering that if people knew how many assumptions went into designing a bridge, they’d never dare cross one. In engineering the abstractions are even more abstract, but quite useful nonetheless.
Are there simply two cultures among programmers? Along similar lines as the two cultures of mathematics? One motivated by the process itself, by esthetics, by abstractions, ideas. The other by solving problems. And then obviously these two cultures react very differently to AI.
I don't know, I learned to like agentic programming. It felt intimidating at first, but now I fully embraced it. Granted I am still anxious what will happen to the developer job market, but for my own projects agentic programming has been a god send.
Programming isn't special, definitely. Programming can be art, writing can be art, painting can be art.
Most programming isn't art, just like most writing, most painting, etc isn't. The programming you do in your day job very probably isn't art. The programming you do for a demoscene program, in my opinion, definitely is.
I think you can agree or disagree with this post; I expect most to disagree now, though I agree.
But either way, look at how readable this post is, and consider whether AI-powered writing gets even slightly close to that ability to provoke agreement or disagreement.
I instinctively want to agree with this but I feel like there's some pretty jarring logical jumps made to equate programming to the more obvious art forms that people put time into ~because~ they want to artistically express themselves.
What the author really wants to say isn't "programming isn't special" but that "programming is art to the same extent as music or painting because people do both things for money within capitalism" which I just don't think holds up.
> Programming isn’t special. It’s just Art, and Art is the most human — and thus, the most universal — thing that there is.
The OP may be fortunate to have worked on stuff that required some kind of artistic thinking, but the vast majority of code produced—as the vast majority of illustrations—is not art but a means to an end, namely providing value to users and stakeholders, and to generate profits.
You didn't read the article. He literally talked about the essence of art being the dutiful practice of the mundane as the only reliable path to brilliance.
The post is well intentioned, but misses the point.
While you can engage in the act of programming from the angle of craft and while you may have started to code because you really enjoyed how it felt like solving a puzzle, programming is primarily a profession. It is a lot closer to accounting than to painting.
There is still space for coding without AI, stuff like advent of code, etc. While it may sound old fashioned as a lot of people did it to practice code challenge for interviews, some did that simply for the pleasure of coding.
But when your job is working in some system for a corporation, big or small, there's no space there for craft or passion, just the reality that what matters is the sausage, not what went into making it.
You may (and probably should) still care about certain engineering principles; correctness, performance, readability, maintainability, etc. But that's about it, whether you write the code or an LLM does is immaterial.
Why? Is it because most programmers can get paid from a company and not most drawers or musicians? Is it that programmers don't give enough free code on Github, or that their PRs don't wax and wane about how beautiful they found their specific bugfix to be?
If you see the whimsical in a PR changing some column name in a table in a billing system, or you feel the magic and fantasy of a REST API, or yet, God forbid, the emotional undertones of fixing a NPE because the previous change did not consider that a field was optional, then you may have trouble to perceive the difference.
I, at least, never wrote a stock management system to explore the depth of human emotions.
Hmm. I had an issue once with numpy shape mismatch errors appearing after 18+ hours of computation. Frustrating, because it could be caught at compile time.
Later, I learned some typelevel programming (in Scala), and by encoding a digital (binary) adder and multiplier at the type level, I showed -- at least to myself -- it was possible to compute and check linear algebra shapes at compile time (without a compiler plugin). It was rather magical and funny to think that I just embedded basic digital logic in such a higher-abstraction world.
It was slow for the inputs I cared about, so I added some optimizations, like an if-statement at the type level, for example, so that it bit-shift for multiplying powers of 2 (multiplication for tensor products). The compile time difference being palpable was a testament to how "some 'ideas' are surprisingly close to others" (err, 'ideas' ~ 'numbers' in this case). There is a connection to the p-adic numbers here, courtesy of dyadics, and some connection to the more-natural "last-mile" problem.
I agree that solving logic puzzles is very fun. I even pointed at things such as Advent of Code in my original reply. Computer programming can be very fun and satisfying to do. It is the reason why I became a software developer.
But it is not the same sort activity as writing a short story, or composing a a symphony, or painting a still-life. Those are done with different purposes. Art is something done with the purpose of exploring emotions, aesthetic beauty, question societal norms, etc.
The closest programming gets to that is if you are writing a jingle for advertisement, or drawing a signpost, or writing a technical article.
I disagree. It's not just a logic puzzle. If I haven't communicated that to you, that's also my failure. I've written stories short and long as well. It's a different kind of art.
"Art is something done with the purpose of exploring emotions, aesthetic beauty, question societal norms, etc."
I apologize if my emotions and aesthetics are not communicated, but I can only say that they were there. As for societal norms, I doubt that "embedding digital logic in types" is a "norm" of the programming society.
And though it's an appeal to patterns, I will have to bring up the general repeated failure of humanity to recognize art.
I apologize if I don't have the same sort of emotional response to embedding linear algebra validation at the compilation step as I do when I watched Mononoke Hime, or when I read The Picture of Dorian Grey.
While your tale sounded pretty interesting, it is the same sort of interesting as solving a math puzzle. I enjoy math puzzles.
Yep, and that's fine. I just think that for the people who do treat something as art, that I'd want to respect their opinion and emotions. Photography was not art, and now is.
Whatever moves people, however people wish to express themselves, whatever people find beautiful, all that is "art" to me. There's much which is art to others, perhaps, that I would not understand as art for myself.
I have to disagree, because this would stretch the meaning of the word "art" ao much that it becomes meaningless. Given your definition, anything can be art. Filing my taxes can be art, sweeping the floor can be art, taking out the trash can be art, making a butt print in my office chair can be art.
Art is something done with the express purpose of aesthetic appreciation, eliciting emotional responses and so on.
Nature for example can be beautiful, and certainly can draw out emotional responses from people. But unless we bring religion into the mix, it is not made with any purpose, it simply is.
The closest thing I think of programming as art is obviously videogames, if I consider that game mechanics are added with the undeniable purpose of inspiring in the player emotional response, it can certainly be done with aesthetics in mind, and I can think of a few examples where it is used to question norms.
"making a butt print in my office chair can be art." -- There were literally butt prints displayed at the Whitney a couple months ago. Just because it's in resin, so what? If I have fun making butt prints on my chair, is that worse because I didn't seal the form?
People in this thread not reading the article and expressing their point of "the 10th api you've written for a business is not art" as if the points of mundanity are not addressed in the article is infuriating.
Edit: why would anyone flag tfa? There is no anti-flag vote right?
"Artists understand that AI is bad for art." Art is in the eye of the beholder, don't tell me what makes for bad art.
You know what AI is bad for? Menu's. Our butcher just send out a pamphlet with discounts for the week. There is sushi on it that looks like plastic covered in slabs of candle wax, inside is avocado but only at first glance, when you look closer it looks more like a mushy bean. The nori looks covered in sesame seeds, but on closer inspection the seeds form a network, like a fungus. In my head I can just feel the horrible mouthfeel when I look at the image. Weird that I find it so disgusting. It seems that some people do, some don't really see the problem with it.
I also recently say on a banner on a Vietnamese restaurant a shrimp.. But only at first glance, because a shrimp is not a full taurus, like a pink striped donut.
sounds like art people clueless about engineering again
And also we do worry, but not in "replacement" way but just "using AI to create bad code with no proper oversight". It's absolutely enabling clueless to develop crap apps
So much of what's going on with a lot of open source community reaction to AI is often just gatekeeping masquerading as morality.
Many of us have spent our adult and teenage lives learning an arcane magic that we took pride and joy and status in. Only to find now it's not so magic anymore. Or not in the way we thought.
I often see parts of my own code as art. Especially when I was younger, I guess.
But I also saw lots of it as: making a living. And there's fluidity between the two.
They're right "programming isn't special" -- it's not the magic you thought it was. It never was. It just appeared magic because others couldn't do it.
You can still have that magic in pockets. But you shouldn't expect to be venerated for it. You never should have.
I've been doing it for 40+ years at this point. I'm happy to let the machines take over a lot of the grunt work so I can get one with making beautiful interesting systems. I can make all things I wanted to make now.
Art is special. Programming... no, get over yourself. You can see it that way. Not everyone else has to. And playing Butlerian Jihad isn't going to dam the flood.
To many, it is just another tool in the toolbox to solve a problem, to get from A to B. I find coding rewarding, in the same way I find puzzles rewarding. But if I had any advise, it would be not to let it define you as a person.
> Artists understand that AI is bad for art. Why don’t programmers understand that we are artists?
imo, that's happening because 2 cultures formed under extremely opposite incentives - "I do stuff and anyone else also doing it is taking my money away from me" vs "Please someone else do same thing as me, it would be so awesome/easier"
the closest art-relating thing to GPL ideals are fanfics. And opinion about ai-generated fanfics has been much closer to our coders view - "sure a lot of it is bad, maybe there's also too much of it, but... there's also some good stuff, so it's good?"
Is it your contention that artists are in the first camp!?
You don’t know many artists if it is. 21st century art, especially, could hardly be more inclusive. Artists are desperate for people to be able to learn to express themselves. Indeed, widening access to art is the motivation of almost all arts funding and patronage (which is what the anti-copyright people think artists should be content with)
Copyright is not gatekeeping. It is just how artists earn for their work that is intended for a mass (or commercial) audience.
Artists are, in general, extremely keen for there to be more art, more artists and more opportunities for artists. It’s not inconsistent with them wanting those artists to do their own work; indeed that is an essential part of it.
I'm saying artists don't want anyone doing *the same art they do*
GPL ideal gives everyone ability to copy-paste and expand anything, with only obligation to allow everyone to do the same to you. Artists culture is far removed from that
---
even more than that, I see people arguing for MIT(!) to lessen the legal burden on fellow programmers
that's the kind of cultural difference I want to point out
It’s not, particularly. Plenty of credited remixing, artistic references, echoes, parodies, pastiches, collaborations, licenses, rolling memes, all sorts of stuff. There’s quite a lot of CC0 stuff out there too.
The permissions (cultural or otherwise) are different depending on the reuse, but no artist minds a credited remix. People just don’t like theft.
I think that AI is the best thing that happened to art. It elevated _all_ human art to this mystical realm. All human work became sacred, as it is unique and bears the Secret Fire. Whatever you do as "art", as long as you didn't use AI, it automatically bears the sacral stamp. Can go to a gallery, whatever. All human art is now elite art.
Here come a thread where those with stock in AI and AI glazers will agree with the title and put forth their claims as if they're obvious and factual, and those against it will do the opposite.
Very stinky topic to be honest and all the posts here are basically the same level of drivel as political discussions.
Programming is different from art or writing in that nobody gives a fuck about the code, only the results—the benefits it brings them. Programming is an industrial process, not an art form.
Ten years from now "programmer" will describe machines and mechanical processes, not people, in a tradition similar to what happened with "computer" after the 1940s.
I think most people here are probably missing his reference, because it's quite apt. "Computers" were, for centuries, a whole class of people whose job involved doing calculations for all sorts of processes - astronomical, mathematical tables, and much more. I'm certain many of them had an absolute love in working things out, a preference for elegance, and much more.
But in the end? All that 'really' mattered was their final product, and once it could be automated - we quickly reached a point where most people no longer even know these people existed. I suspect many of the exact arguments made in argument of the longevity of programmers of today were probably also made about the longevity of computers in the past, as it became clear that 'computing machines' would be able to complete much of the same work.
Ten years from now, there will still be both human programmers and people who don't understand why they are needed. (I'd make a case as to why that is, but I'm replying to a comment that just states the opposite without explaining why, so I don't feel the need to.)
Programming by humans will become a handicraft, something people indulge in in their spare time because it's "retro" or interesting or whatever. Like knitting or weaving by hand, or programming in BASIC on a C64. I mean to use the "computer" example again, people still do arithmetic by hand, and even learn tricks to better do it in their head.
But no serious software will be written by humans in ten years. It will not be a profession.
> I guess the same can be said about plumbing and HVAC installations.
I feel like both of those have fewer paths to a successful end-product, and minor issues in the final product are way more visible to the users thereof.
We tend to have a pretty high tolerance for minor software "quirks", unlike if the hot water system or the drains start acting up...
Strange. That's like saying no one cares about the technicals of art, just how they feel about looking at an image.
As a consumer of graphics and music, let me "agree" for just a moment. I might not care how the music or image came to me. I just care that I like the final product. Which is why most paintings are trash, because I prefer highly saturated colors.
...I suppose this is somewhat true of many people already.
> Programming is different from art or writing in that nobody gives a fuck about the code, only the results—the benefits it brings them. Programming is an industrial process, not an art form.
Not necessarily. There are niches in programming that I think could count as art (e.g. live-coding, algoraves) where the programming as performance and the visualized code become part of the artwork. But I think this is not what the OP has in mind.
Maybe programming needs to die first, to be able to be elevated to an artform.
Nah. Programming is utilitarian, not artistic. While programmers can do their best to produce elegant, well-ordered and designed code they are producing a means to an end: the program has a purpose beyond being elegant, well-ordered and designed. If the clankers can produce programs which fulfil the same purpose and can do it reliably while taking less time and resources - a big if - they are the way to go for most programs. Cameras largely replaced painters for the purpose of producing portraits, photographers control the cameras to make them produce the desired outcome. Clankers will largely replace programmers for the purpose of producing code, we may need a new term to indicate the humans who control them.
I’ve always been dumbfounded by programmers who believed they were being paid by business to “write code”. Maybe get your head out of your asses and sit in a few meetings where the requirements are being generated from. You’d quickly realize no one has ever cared about “the code” that was always an inconvenient time and money wasting means to an end.
The bricklayer building my house may have the most incredibly aesthetic application or mortar during the process, but all I care about is the wall staying up.
Are they practising an art? Surely. Is it relevant? Nah.
So who do you hire if all you'll see is a wall that is up? The one that seems to care whether it'll stay up after they're gone, or the one who's objective it is to get it up for the price you want to pay?
"You've got to make the back of the fence, that nobody will see, just as good looking as the front of the fence. Even though nobody will see it, you will know, and that will show that you're dedicated to making something perfect." — Paul Jobs
The person you hire can be an artist of the highest degree, making the prettiest fence on the planet, caring about the project the entire time, and it could fall down in a brisk wind.
Half shaved alcoholic Barry could slap some bricks together with a cigarette hanging out his mouth and it’ll last a century.
Aesthetics and utility are not always as correlated as you might hope.
When something is brought into the world through human intention, it has the possibility of being art. A human must stand next to it and say "This is mine."
The human role in the creation of art is non-negotiable.
Is a print of the Mona Lisa still art? Or is it worthless slop by virtue of having been created by a machine?
C’est ne pas une ~~pipe~~ Mona Lisa
https://en.wikipedia.org/wiki/The_Treachery_of_Images
as of yet, there’s still no such thing as a print created entirely by a machine. Someone made the scan, prepared the print file, chose the paper stock, proofed the prints. Or at least some of those steps, depending on the print.
The point is, there’s no as a print that is 1:1 equivalent to an original painting. There are artistic choices embedded throughout the process that influence the result and make some prints “better” than others.
It’s easy to assume an image is just an image, a bunch of pixels with different numerical color values. But the real world has so much more detail than that.
For the curious, Jean Baudrillard and Walter Benjamin are a good place to start for answering these questions.
There's not one answer.
IMO the original painting is art, a faithful copy is also lesser art, but a print is not art, because it takes significantly less skill and creativity to print thousands of it. It isn't worthless nor slop, though.
Basically, art speaks to our sensibilities, so we expect to find a message in there. LLMs can't create, only mix-and-match what exists in their training data set. You could slop a new painting, make a special canvas printer, and exhibit it in a blind test. Some people will think it's art because they find meaning in it, while others will think it's not art because they'll recognize several meanings slopped together in a nonsensical way.
In reality, it was never art, because the creator, a statistical algorithm, never had any message to convey in the first place.
It’s a print of a piece of art.
I am a programmer who likes aesthetics. I think about how aesthetic it is to not have to deal with certain production incidents for certain blocks of code because the typelevel computation tells me it would be a compiler bug if it screwed up. I like the feeling of realizing those 100 LOC could just be 10.
I sometimes tell people of when I came down from Mt. Fuji, there were wispy clouds and grand nature below me, picturesque like a painting. At that time, I likened it to the beauty I felt when I was first learning Haskell. But I say it because I expect it to be a rare kind of sentiment.
The thing with art and music is that they are easy to appreciate, and the appreciation grows deeper with more consideration. I love reading the placards in museums and attempting to understand why the artist did what they did, I like it more than even looking at the piece itself.
Code (and math, for that matter) is almost the same except for one key difference: they are not easy to appreciate without deliberate training, training which is often far to the side of anything most people need/want to deal with.
> The thing with art and music is that they are easy to appreciate
I get what you mean (and agree w.r.t. math/code) but notably, I think appreciation for a lot of things still accumulates if you put in the work.
As an amateur violist, I can attest that I gained a totally new appreciation for most of the pieces I've studied and played in an orchestra in the past.
This not only includes "unknown" classical music from different eras, but also the obvious (popular) candidates like Beethoven's 6th, Dvořak's 9th and Grieg's "Peer Gynt" suites.
And there's a lot of great music one needs to get into first; for expample: I love Tool songs exactly for that, and there are certainly more obscure artists :)
So, I suspect the thing about maths and code is mainly just caused by the fact that people can go through life just fine without really interacting with them on the level required to develop the smallest bit of "taste" (as opposed to e.g. music).
> The thing with art and music is that they are easy to appreciate
> Code (and math, for that matter) is almost the same except for one key difference: they are not easy to appreciate without deliberate training, training which is often far to the side of anything most people need/want to deal with.
I would argue that this exists on a spectrum. There's lots of art and music that's pretty difficult to appreciate without deliberate training, and indeed there are whole categories of music which we would probably call music for musicians.
For example, the album Kind of Blue by Miles Davis is loved by many and is considered by most people to be the best gateway record into the world of jazz, because it's easy to listen to and appreciate. An album like Sketches of Spain, and especially an album like Bitches Brew, are more difficult for the average non-musician listener to get into.
An even more out-there example for music is Allan Holdsworth. In certain circles, he's a well-known and well-regarded name, considered highly influential. Most people have no idea who he is or what he did. (A bit like that cutaway in Family Guy where they jumped to Benjamin Disraeli and he simply said: "you don't even know who I am!").
Similarly, in art and painting, you often need training to understand why something was especially impressive. Now that we have photography, some old paintings can feel "boring" if you don't know how to appreciate the level of difficulty in producing a near-photorealistic work in the 1700s.
Conversely, some math is very easy to appreciate without training! I had a buddy who I got excited about math simply by explaining the Fibonacci sequence and the golden ratio, then showing trivial examples of how they appear in nature. My friend got lit up about math that day in a whole new way.
Coding is not really programming. It is certainly a highly adjacent skill, but coding is not the same as programming. To quote Leslie Lamport, coding is to programming as typing is to writing.
A key difference is we are not paid to goto mt.fuji. the opposite infact.
Hence we can't take this lesson to the workplace.
A lot of arts can be done as a job.
And it's always a mixed blessing.
A collective of workers in a field can very much decide what they want to get payed for. Craftsmen did exactly that for centuries, and that's in fact what makes them being known for quality and is thus in fact their business moat.
Programming as an art form always reminds me of the Einstein quote; "Pure mathematics is, in its way, the poetry of logical ideas". Both are just art forms you cannot appreciate without some understanding of it. Arguably thats true of all art actually, its just that the more familiar forms, like painting or music, can be understood at a basic level without an understanding, whereas mathematics and programming are essentially alien to the casual observer.
This is so tediously shallow.
Sure, some programming might be art. I've written programs that could qualify. But most isn't, unless you also want to count preparing a balance sheet for a corporation as art. Get over it.
I wish I could find the quote, I think it was on C2 Wiki, but alas, it was something like:
If you're an artist, programming is your clay, if you're an engineer, programming is your building material.
Point being, which I always connected with, was that programming is a medium for expressing a lot of things. Just like you can use paper and pen to write poetry or a dry technical manual. And everyone gets to decide how they see it and use it.
I am so fascinated about this angle -- whether programming is art or not. This is one of the things that got me to HN recently and I love reading these discussiong as a non-programmer.
While I love art, I am not an art historian or critic, so the definition I have for it is highly subjective -- in my opinion one of the functions of art is communication with other people (often through time and space). For art to fulfill its telos, so to speak, the message that it carries must also be read (heard, perceived) by somebody and then, if it's great art, eventually someone would want to respond to it.
The message can be simple, complex, subversive, stupid, clever, it can be an observation about world, a joke, a profound truth, a memory, a question, a snapshot, a curiosity, a trick, and a ton of other things. And sure, the message can be distorted, misunderstood, twisted, forgotten, lost, etc, but if no one "reads" it and no one "talks" to it, it might as well be glossolalia.
So my question for folks who do consider programming art -- do you "read" other people's code like this? Do you exchange ideas through code? Have you ever trolled great coders of the past through your code or tried to prove them wrong?
I hope my question doesn't come off as complete nonsense.
P.s. I know that there are programming manifestos which to me sounds like there is a layer of meaning that the code carries and this meaning goes beyond pure machine instructions or software functionality, but I'd love to read answers of actual programmers.
> So my question for folks who do consider programming art -- do you "read" other people's code like this? Do you exchange ideas through code? Have you ever trolled great coders of the past through your code or tried to prove them wrong?
Yes, 100% yes. I have always said that I reading someones code to me is akin to reading a personal diary or memoir. It exposes so many thing about their frame of mind and world view. I consider it beautiful and the advent of LLMs greatly muddying this signal (it has absolutely not REMOVED IT) has been incredible painful.
I strongly agree that programming is art, but I think there's a difference between other art forms.
A novel is both how it's made and what it is, and so is a piece of music.
Programming produces two different outputs: the code and the program. What users consume, and care about, is the program. The code may or may not be read by other programmers but it's not the main output. (It would be extremely weird to output code in a language that can't ever be run.)
And so I think the beauty or effectiveness of the program matters more than the beauty or elegance of the code. Those are not entirely orthogonal of course, but only loosely coupled.
A programmer should care a lot about the program, and a little less about the code. Vibe programming (where the programmer doesn't care one way or another) to me is a crime; but you can certainly use AI to code, and still care about the finished product, and make it good.
> A programmer should care a lot about the program, and a little less about the code
This gives me vibes of like saying to artists "you should care about the painting but less about the brushes and paints"
The tools you choose and the lines you scribe all contribute to the whole. It all matters to some extent
We’re in automation. The point of programming is not to do the same thing again.
The role of a developer (and most IT roles), at its core, is to make yourself obsolete, move on, rinse and repeat.
Feature / scope creep may have blindsided some.
I’m happy most programming is going away. I was capable but now I’m even more capable at creating solutions. The art will stay.
> The point of programming is not to do the same thing again.
That's called an abstraction, which AI is expressly not. If your work involves writing the same code over and over again, you're doing it wrong.
> I’m happy most programming is going away. I was capable but now I’m even more capable at creating solutions.
This describes management.
> The art will stay.
This describes actual engineering.
Why isn’t AI a complex form of abstraction?
It works because it re-uses previous work to solve new problems. That is what abstractions are used for.
From a previous comment, vis-à-vis compilation vs. code generation:
> High-level programming languages use well-defined, limited syntax to encode program behavior in a deterministic way. Compilers translate these directions into programs that should have identical behavior between compiler runs and between different compilers. (If they don't, that's a compiler bug, or else an artifact of UB.) This means you can structurally and provably rely on the high-level programming layer without worrying about what's underneath: the assembly is abstracted away. You also get the massive benefit of being able to tweak and improve the assembly layer independently of the programming language layer, so long as the contract between language and compiler is not violated.
> If AI is a "layer of abstraction," so is working with a bunch of contractors to make your app. The definition is broadened to the point of absurdity. (Solely: "I don't have to think about code anymore," which only touches on the most superficial aspect of an abstraction.)
If there was a way to get a reproducible, deterministic mapping between natural language and code by way of a LLM, that would be an abstraction. But... that's just called a programming language (specifically a transpiler).
Programming is special in the sense that it is one of those direct experiences of mere language instructions being used to make things work - a form that resembles incantations and sorcery of the old times.
Of course there are many other indirect instances of language being used as the primary tool to move, but programming happens to be a direct raw unadulterated first hand experience into building things with nothing but raw language primitives.
Where code is ideas willed into existence.
Before AI, some programming could be considered be considered art. There are definitely codebases that are more beautiful than others. But now with introduction of AI you can’t consider any code as art as you have no idea who produced it. Yes, it may be looking good, but from that perspective it’s just randomly produced without the thought of being art. And at some point it will be refactored into oblivion by something that doesn’t care.
Said this in a thread already but bears repeating at the top level:
Coding is not Programming
Coding is certainly a highly adjacent skill to programming, but coding is not the same as programming.
To quote Leslie Lamport: "coding is to programming as typing is to writing."
I agree, and I've considered my code to be art for a long while. Take for example my coffeescript parser: https://github.com/jaekwon/JoeScript/blob/master/src/joescri...
This is art.
And I have much love for good frameworks and design.
I'm fortunate to have started gno.land before AI, yet just late enough to finish it with AI. The GnoVM (gno.land) is also art -- go interpreting go, but in a novel multiuser context, a re-imagining of TBL's WWW in Go and markdown. AI was used for final touch polishing. Couldn't have ended up any better.
AI is not yet there to grok the artistry of code. But it will eventually, and humanity will benefit from it necessarily, not because it is demanded, but because people like us desire it. Push forward.
Well written article.
--
p.s. plug: gno.world, find me there.
Programming can be art in the way that cooking can be art.
Most of it is in fact NOT art but simply done to solve a problem.
Right on. And similarly, you don't need to learn farming to be able to cook good food, just like you didn't need to know assembly language or machine code to be able to write programs before AI.
I don't see it. Programming CAN be used to generate art, but is not an art by itself.
I cannot imagine lines of code be exhibited in a museum. I can appreciate smart or witty solutions for a problem, but that is not what art is. I can appreciate a quick solution for a Rubik cube, I can even see the Rubik cube itself in a museum, but I cannot imagine the steps or instructions for that quick solution in a museum (unless that paper has historical significance).
There are different kind of arts. There is the art of a craftsmen and there is beautiful art. The former is rarely exhibited in museums unless is also has an historic value. It's the kind of excellence with that you do your work and it can be in fact in every kind of work you do.
> There are different kind of arts. There is the art of a craftsmen and there is beautiful art.
The art of a craftsman, otherwise known as 'craft'.
Neither poetry nor literature is displayed in a museum (or at least that's not their normal home). But no one argues that they aren't art.
You've never been to the Bodleian, have you?
Here are a couple counter-points that come to mind:
Linus explaining taste in code: https://www.youtube.com/watch?v=78Y17hAo96I
Fast inverse square root https://en.wikipedia.org/wiki/Fast_inverse_square_root
Being a humble rank-and-file programmer I did produce pieces of code that I will be proud forever as well, e.g. this snippet to control the length of $PWD in bash that I still use almost unchanged 25 years later:
I agree, is the 100th rest api I’ve made for my 5th employer art? I don’t think so. It’s just a way to (maybe) make my employer money.
I’d say the brainfuck language on the other hand is art. Hard to draw a fine line as to which is which.
I can say most if not all the projects I’ve ever made land in the former. I’ve made some clever solutions but nothing approaching something with meaning.
I believe it's a spectrum, just like there is a whole spectrum between the Mona Lisa and a generic flyer for your local bowling alley.
There can be beauty in even the smallest of things. You can tell alot about a person by how they choose to structure even down to the loops and methods.
Writing by itself isn’t art, but poetry and literature are. And, by the same token, I don’t expect most works of literature to be exhibited in a museum — books are easily copied, so there’s little value to just having the book’s text in a museum.
Works like the Black Perl[0] are decidedly artistic in nature. Demos (in the demo scene sense) are an artistic endeavour. Competitions like the Obfuscated C Contest or the Underhanded C Contest are very much judged on aesthetics.
0. https://en.wikipedia.org/wiki/Black_Perl
> I cannot imagine lines of code be exhibited in a museum.
Honestly, I can. The author of this article wrote Twisted. I certainly can imagine a museum where computer history is explained along with all the software achievements that made a huge impact on software engineering as a whole, and Twisted would have a place in it.
You don't have to imagine it
The printed Apollo program code is owned by a museum (https://airandspace.si.edu/) and is on display there sometimes
There may be others elsewhere too, but that one jumped to mind immediately
Programming is special, as it's basically translation on steroids.
I don't know what other profession weaves so many levels of abstraction to get to the final product.
Well, "translator" was one of the first jobs to be lost to AI.
There's a 'joke' in engineering that if people knew how many assumptions went into designing a bridge, they’d never dare cross one. In engineering the abstractions are even more abstract, but quite useful nonetheless.
Are there simply two cultures among programmers? Along similar lines as the two cultures of mathematics? One motivated by the process itself, by esthetics, by abstractions, ideas. The other by solving problems. And then obviously these two cultures react very differently to AI.
I don't know, I learned to like agentic programming. It felt intimidating at first, but now I fully embraced it. Granted I am still anxious what will happen to the developer job market, but for my own projects agentic programming has been a god send.
Apparently, neither is coherent writing.
If you’re going to call this “incoherent”, which IMO it is not, you should expect to be asked by someone to explain why.
So I am.
Programming isn't special, definitely. Programming can be art, writing can be art, painting can be art.
Most programming isn't art, just like most writing, most painting, etc isn't. The programming you do in your day job very probably isn't art. The programming you do for a demoscene program, in my opinion, definitely is.
I think you can agree or disagree with this post; I expect most to disagree now, though I agree.
But either way, look at how readable this post is, and consider whether AI-powered writing gets even slightly close to that ability to provoke agreement or disagreement.
I instinctively want to agree with this but I feel like there's some pretty jarring logical jumps made to equate programming to the more obvious art forms that people put time into ~because~ they want to artistically express themselves.
What the author really wants to say isn't "programming isn't special" but that "programming is art to the same extent as music or painting because people do both things for money within capitalism" which I just don't think holds up.
> Programming isn’t special. It’s just Art, and Art is the most human — and thus, the most universal — thing that there is.
The OP may be fortunate to have worked on stuff that required some kind of artistic thinking, but the vast majority of code produced—as the vast majority of illustrations—is not art but a means to an end, namely providing value to users and stakeholders, and to generate profits.
You didn't read the article. He literally talked about the essence of art being the dutiful practice of the mundane as the only reliable path to brilliance.
Everyone in the comments snitching on themselves for not reading.
The post is well intentioned, but misses the point.
While you can engage in the act of programming from the angle of craft and while you may have started to code because you really enjoyed how it felt like solving a puzzle, programming is primarily a profession. It is a lot closer to accounting than to painting.
There is still space for coding without AI, stuff like advent of code, etc. While it may sound old fashioned as a lot of people did it to practice code challenge for interviews, some did that simply for the pleasure of coding.
But when your job is working in some system for a corporation, big or small, there's no space there for craft or passion, just the reality that what matters is the sausage, not what went into making it.
You may (and probably should) still care about certain engineering principles; correctness, performance, readability, maintainability, etc. But that's about it, whether you write the code or an LLM does is immaterial.
Why? Is it because most programmers can get paid from a company and not most drawers or musicians? Is it that programmers don't give enough free code on Github, or that their PRs don't wax and wane about how beautiful they found their specific bugfix to be?
If you see the whimsical in a PR changing some column name in a table in a billing system, or you feel the magic and fantasy of a REST API, or yet, God forbid, the emotional undertones of fixing a NPE because the previous change did not consider that a field was optional, then you may have trouble to perceive the difference.
I, at least, never wrote a stock management system to explore the depth of human emotions.
You have missed out on _why, perhaps? I am old enough to remember him, and Camping, and the chaotic, brilliant nature of his work.
Hmm. I had an issue once with numpy shape mismatch errors appearing after 18+ hours of computation. Frustrating, because it could be caught at compile time.
Later, I learned some typelevel programming (in Scala), and by encoding a digital (binary) adder and multiplier at the type level, I showed -- at least to myself -- it was possible to compute and check linear algebra shapes at compile time (without a compiler plugin). It was rather magical and funny to think that I just embedded basic digital logic in such a higher-abstraction world.
It was slow for the inputs I cared about, so I added some optimizations, like an if-statement at the type level, for example, so that it bit-shift for multiplying powers of 2 (multiplication for tensor products). The compile time difference being palpable was a testament to how "some 'ideas' are surprisingly close to others" (err, 'ideas' ~ 'numbers' in this case). There is a connection to the p-adic numbers here, courtesy of dyadics, and some connection to the more-natural "last-mile" problem.
It's not REST, maybe. But I felt it was magical.
I agree that solving logic puzzles is very fun. I even pointed at things such as Advent of Code in my original reply. Computer programming can be very fun and satisfying to do. It is the reason why I became a software developer.
But it is not the same sort activity as writing a short story, or composing a a symphony, or painting a still-life. Those are done with different purposes. Art is something done with the purpose of exploring emotions, aesthetic beauty, question societal norms, etc.
The closest programming gets to that is if you are writing a jingle for advertisement, or drawing a signpost, or writing a technical article.
I disagree. It's not just a logic puzzle. If I haven't communicated that to you, that's also my failure. I've written stories short and long as well. It's a different kind of art.
"Art is something done with the purpose of exploring emotions, aesthetic beauty, question societal norms, etc." I apologize if my emotions and aesthetics are not communicated, but I can only say that they were there. As for societal norms, I doubt that "embedding digital logic in types" is a "norm" of the programming society.
And though it's an appeal to patterns, I will have to bring up the general repeated failure of humanity to recognize art.
I apologize if I don't have the same sort of emotional response to embedding linear algebra validation at the compilation step as I do when I watched Mononoke Hime, or when I read The Picture of Dorian Grey.
While your tale sounded pretty interesting, it is the same sort of interesting as solving a math puzzle. I enjoy math puzzles.
Yep, and that's fine. I just think that for the people who do treat something as art, that I'd want to respect their opinion and emotions. Photography was not art, and now is.
Whatever moves people, however people wish to express themselves, whatever people find beautiful, all that is "art" to me. There's much which is art to others, perhaps, that I would not understand as art for myself.
I have to disagree, because this would stretch the meaning of the word "art" ao much that it becomes meaningless. Given your definition, anything can be art. Filing my taxes can be art, sweeping the floor can be art, taking out the trash can be art, making a butt print in my office chair can be art.
Art is something done with the express purpose of aesthetic appreciation, eliciting emotional responses and so on.
Nature for example can be beautiful, and certainly can draw out emotional responses from people. But unless we bring religion into the mix, it is not made with any purpose, it simply is.
The closest thing I think of programming as art is obviously videogames, if I consider that game mechanics are added with the undeniable purpose of inspiring in the player emotional response, it can certainly be done with aesthetics in mind, and I can think of a few examples where it is used to question norms.
"making a butt print in my office chair can be art." -- There were literally butt prints displayed at the Whitney a couple months ago. Just because it's in resin, so what? If I have fun making butt prints on my chair, is that worse because I didn't seal the form?
People in this thread not reading the article and expressing their point of "the 10th api you've written for a business is not art" as if the points of mundanity are not addressed in the article is infuriating.
Edit: why would anyone flag tfa? There is no anti-flag vote right?
"Artists understand that AI is bad for art." Art is in the eye of the beholder, don't tell me what makes for bad art.
You know what AI is bad for? Menu's. Our butcher just send out a pamphlet with discounts for the week. There is sushi on it that looks like plastic covered in slabs of candle wax, inside is avocado but only at first glance, when you look closer it looks more like a mushy bean. The nori looks covered in sesame seeds, but on closer inspection the seeds form a network, like a fungus. In my head I can just feel the horrible mouthfeel when I look at the image. Weird that I find it so disgusting. It seems that some people do, some don't really see the problem with it.
I also recently say on a banner on a Vietnamese restaurant a shrimp.. But only at first glance, because a shrimp is not a full taurus, like a pink striped donut.
> what it’s doing to our industry, but we are using it anyway
Other industries are using it too. It's quite delusional to assume that just because people hate something they won't use it.
sounds like art people clueless about engineering again
And also we do worry, but not in "replacement" way but just "using AI to create bad code with no proper oversight". It's absolutely enabling clueless to develop crap apps
Why is this flagged? I find it a fair essay. Why do philistines get to spoil all the fun around here?
So much of what's going on with a lot of open source community reaction to AI is often just gatekeeping masquerading as morality.
Many of us have spent our adult and teenage lives learning an arcane magic that we took pride and joy and status in. Only to find now it's not so magic anymore. Or not in the way we thought.
I often see parts of my own code as art. Especially when I was younger, I guess.
But I also saw lots of it as: making a living. And there's fluidity between the two.
They're right "programming isn't special" -- it's not the magic you thought it was. It never was. It just appeared magic because others couldn't do it.
You can still have that magic in pockets. But you shouldn't expect to be venerated for it. You never should have.
I've been doing it for 40+ years at this point. I'm happy to let the machines take over a lot of the grunt work so I can get one with making beautiful interesting systems. I can make all things I wanted to make now.
Art is special. Programming... no, get over yourself. You can see it that way. Not everyone else has to. And playing Butlerian Jihad isn't going to dam the flood.
To many, it is just another tool in the toolbox to solve a problem, to get from A to B. I find coding rewarding, in the same way I find puzzles rewarding. But if I had any advise, it would be not to let it define you as a person.
> Artists understand that AI is bad for art. Why don’t programmers understand that we are artists?
imo, that's happening because 2 cultures formed under extremely opposite incentives - "I do stuff and anyone else also doing it is taking my money away from me" vs "Please someone else do same thing as me, it would be so awesome/easier"
the closest art-relating thing to GPL ideals are fanfics. And opinion about ai-generated fanfics has been much closer to our coders view - "sure a lot of it is bad, maybe there's also too much of it, but... there's also some good stuff, so it's good?"
Is it your contention that artists are in the first camp!?
You don’t know many artists if it is. 21st century art, especially, could hardly be more inclusive. Artists are desperate for people to be able to learn to express themselves. Indeed, widening access to art is the motivation of almost all arts funding and patronage (which is what the anti-copyright people think artists should be content with)
I've seen enough tracing scandals
and some of my favorite works have been shutdown for background art
Copyright is not gatekeeping. It is just how artists earn for their work that is intended for a mass (or commercial) audience.
Artists are, in general, extremely keen for there to be more art, more artists and more opportunities for artists. It’s not inconsistent with them wanting those artists to do their own work; indeed that is an essential part of it.
I'm not arguing about "there being more art"
I'm saying artists don't want anyone doing *the same art they do*
GPL ideal gives everyone ability to copy-paste and expand anything, with only obligation to allow everyone to do the same to you. Artists culture is far removed from that
---
even more than that, I see people arguing for MIT(!) to lessen the legal burden on fellow programmers
that's the kind of cultural difference I want to point out
> Artists culture is far removed from that
It’s not, particularly. Plenty of credited remixing, artistic references, echoes, parodies, pastiches, collaborations, licenses, rolling memes, all sorts of stuff. There’s quite a lot of CC0 stuff out there too.
The permissions (cultural or otherwise) are different depending on the reuse, but no artist minds a credited remix. People just don’t like theft.
basically artists are sellers, while programmers are buyers
creation of new competing products is seen as a catastrophe by sellers, but as more competition by buyers
and our concern as a community basically has been "but do we have enough anti-monopoly protections in place?"
I think that AI is the best thing that happened to art. It elevated _all_ human art to this mystical realm. All human work became sacred, as it is unique and bears the Secret Fire. Whatever you do as "art", as long as you didn't use AI, it automatically bears the sacral stamp. Can go to a gallery, whatever. All human art is now elite art.
Here come a thread where those with stock in AI and AI glazers will agree with the title and put forth their claims as if they're obvious and factual, and those against it will do the opposite.
Very stinky topic to be honest and all the posts here are basically the same level of drivel as political discussions.
This should not be flagged.
Why was this flagged?
I don't think there is anything here for me anymore.
Users flagged it. We've turned the flags off now.
Programming is different from art or writing in that nobody gives a fuck about the code, only the results—the benefits it brings them. Programming is an industrial process, not an art form.
Ten years from now "programmer" will describe machines and mechanical processes, not people, in a tradition similar to what happened with "computer" after the 1940s.
I think most people here are probably missing his reference, because it's quite apt. "Computers" were, for centuries, a whole class of people whose job involved doing calculations for all sorts of processes - astronomical, mathematical tables, and much more. I'm certain many of them had an absolute love in working things out, a preference for elegance, and much more.
But in the end? All that 'really' mattered was their final product, and once it could be automated - we quickly reached a point where most people no longer even know these people existed. I suspect many of the exact arguments made in argument of the longevity of programmers of today were probably also made about the longevity of computers in the past, as it became clear that 'computing machines' would be able to complete much of the same work.
Ten years from now, there will still be both human programmers and people who don't understand why they are needed. (I'd make a case as to why that is, but I'm replying to a comment that just states the opposite without explaining why, so I don't feel the need to.)
Programming by humans will become a handicraft, something people indulge in in their spare time because it's "retro" or interesting or whatever. Like knitting or weaving by hand, or programming in BASIC on a C64. I mean to use the "computer" example again, people still do arithmetic by hand, and even learn tricks to better do it in their head.
But no serious software will be written by humans in ten years. It will not be a profession.
And I will again also state stuff without any supporting argument. In 10 years programming will be done entirely by specially trained ferrets.
> Programming is different from art or writing in that nobody gives a fuck about the code, only the results
Nobody except the programmers, I guess. Quite a few of us care about the craft
I guess the same can be said about plumbing and HVAC installations.
I think art is different from the rest in that it lost utilitarian value. In other words, Art is degenerative by definition.
> I guess the same can be said about plumbing and HVAC installations.
I feel like both of those have fewer paths to a successful end-product, and minor issues in the final product are way more visible to the users thereof.
We tend to have a pretty high tolerance for minor software "quirks", unlike if the hot water system or the drains start acting up...
Strange. That's like saying no one cares about the technicals of art, just how they feel about looking at an image.
As a consumer of graphics and music, let me "agree" for just a moment. I might not care how the music or image came to me. I just care that I like the final product. Which is why most paintings are trash, because I prefer highly saturated colors.
...I suppose this is somewhat true of many people already.
> Programming is different from art or writing in that nobody gives a fuck about the code, only the results—the benefits it brings them. Programming is an industrial process, not an art form.
Not necessarily. There are niches in programming that I think could count as art (e.g. live-coding, algoraves) where the programming as performance and the visualized code become part of the artwork. But I think this is not what the OP has in mind.
Maybe programming needs to die first, to be able to be elevated to an artform.
Nah. Programming is utilitarian, not artistic. While programmers can do their best to produce elegant, well-ordered and designed code they are producing a means to an end: the program has a purpose beyond being elegant, well-ordered and designed. If the clankers can produce programs which fulfil the same purpose and can do it reliably while taking less time and resources - a big if - they are the way to go for most programs. Cameras largely replaced painters for the purpose of producing portraits, photographers control the cameras to make them produce the desired outcome. Clankers will largely replace programmers for the purpose of producing code, we may need a new term to indicate the humans who control them.
I’ve always been dumbfounded by programmers who believed they were being paid by business to “write code”. Maybe get your head out of your asses and sit in a few meetings where the requirements are being generated from. You’d quickly realize no one has ever cared about “the code” that was always an inconvenient time and money wasting means to an end.
The bricklayer building my house may have the most incredibly aesthetic application or mortar during the process, but all I care about is the wall staying up.
Are they practising an art? Surely. Is it relevant? Nah.
So who do you hire if all you'll see is a wall that is up? The one that seems to care whether it'll stay up after they're gone, or the one who's objective it is to get it up for the price you want to pay?
"You've got to make the back of the fence, that nobody will see, just as good looking as the front of the fence. Even though nobody will see it, you will know, and that will show that you're dedicated to making something perfect." — Paul Jobs
The person you hire can be an artist of the highest degree, making the prettiest fence on the planet, caring about the project the entire time, and it could fall down in a brisk wind.
Half shaved alcoholic Barry could slap some bricks together with a cigarette hanging out his mouth and it’ll last a century.
Aesthetics and utility are not always as correlated as you might hope.