I’d extend that to suggest—based on conversations with the artists in my life, anyway—that for many, the friction along the path from an idea to a work is where the art happens in the first place. That the art happens in the additions and subtractions and judgments the artist makes along the way as they bring the artifact into being. That without that, it’s something closer to manufacturing.

I’m reminded of how we around here grumble at piles of vibe-coded slop, even if they notionally solve the users’ problems at hand. It’s not strictly that “it’s insufficient at satisfying the problem brief,” it’s that it’s missing all the other latent considerations—structure, coherence, legibility, maintainability, determinism, good judgment—that a skilled code craftsperson would have worked in along the way almost without thinking.

Depressing for artists of code itself—liberating for the people whose artistic practice is maybe one level of abstraction up—whose obsession is iterating through “finished” products til they fit just so, til they reflect the high-level intention just right. For whom the code part was always an annoying-but-necessary slog, akin to, as another commenter said, grinding the snails for pigment…

“I dread what it means for the code base at work, but damn if I’m not cranking out every single side project I’d never gotten around to…”