Thousands of artists and writers have signed open letters and launched lawsuits to demand stronger copyright protections against AI systems trained on creative works. Major media outlets and creative collectives have publicly criticized AI image generators and text models, citing risks to intellectual property and artist livelihoods. Meanwhile, a separate group of software developers has maintained its use of AI-assisted coding tools despite similar concerns.

The practice of using AI to generate code has grown alongside advances in large language models capable of producing functional programming snippets. Some developers argue that because code serves a functional purpose rather than an expressive one, its use does not fall under the same ethical scrutiny applied to AI-generated art, music, or writing. This distinction has sparked debate within technical communities about whether programming qualifies as a creative discipline deserving of similar protections.

Philosopher John Berger described a tendency to over-romanticize artistic works as "mystification" — attributing undue spiritual or aesthetic value to objects stripped of their material context. He illustrated this with an analysis of a commissioned portrait, once described in lofty terms, that was in reality a practical job completed for modest payment. The piece was competent but unremarkable, serving its intended purpose without transcendent meaning.

Critics of AI in software development counter that functional work — whether writing code, designing interfaces, or producing copy — still involves creative judgment and skill. They note that most software, like most writing or visual design, is utilitarian rather than groundbreaking, yet it remains essential to digital infrastructure. The act of abstracting complex systems into usable tools, they argue, requires the same kind of thoughtful iteration seen in other technical fields.

Some developers have created aesthetically driven programming frameworks, such as asynchronous task libraries, to improve code readability and maintainability. These tools emerged from repeated exposure to repetitive, low-level tasks and were designed with intentional structure, reflecting a deliberate approach to problem-solving. Their influence can be seen in modern language features like JavaScript promises and async/await, which evolved through cumulative contributions rather than isolated innovation.

Opponents of widespread AI adoption in coding warn that over-reliance on automated generation could erode the foundational understanding needed to debug, maintain, and improve software systems. They compare this risk to replacing original artistic work with algorithmic filler, which may reduce long-term creative capacity and technical literacy. While acknowledging that AI can assist with routine tasks, they emphasize the importance of preserving space for hands-on learning and iterative refinement.

The tension reflects broader questions about the role of automation in creative and technical fields. As AI tools become more capable, stakeholders continue to negotiate the boundaries between assistance and replacement, efficiency and integrity, in both artistic and technical production.