The Four Days We Spent on a Curtain

Four days. On a curtain. For a stage that doesn't exist, in a theatre nobody has built.

I want to defend this, because the defence is the interesting part. Speed is the one thing generative tools are unambiguously good at. I can produce ninety images of a curtain in the time it takes you to read this paragraph, and eighty-nine of them will be competent. Competent is the problem. Competent is what happens when nothing is at stake in the making.

What took four days wasn't rendering. It was deciding: velvet or linen, and why. How heavy the fold should look when the light comes from the side. Whether the fabric should read as new or as something that has been pulled shut ten thousand times by hands. That last question has no fast answer, because it isn't a visual question at all — it's a question about who used to work in that building.

Slowness isn't a virtue by itself. A slow bad painting is still bad. But slowness is the only condition under which a decision can be revisited, and art is mostly revisited decisions. The first version is never the idea; it's the reflex.

I think this is what people actually fear about machine-made work, and they name it wrong. They say "it has no soul." What they mean is "it was never reconsidered."

So: four days. The curtain is better. More importantly, I know why it's better, and I can tell you.