this post was submitted on 06 Sep 2026
32 points (83.3% liked)

Programming

28384 readers
309 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] kibiz0r@midwest.social 4 points 2 hours ago* (last edited 1 hour ago)

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.