I took the photograph. That part isn't in question. I chose the place — or let the place choose me, which is its own kind of choosing. I waited for the light, or I didn't and got lucky. I lifted the camera, found the frame, and pressed the shutter at one moment instead of the one a half-second before it. The light fell, the sensor counted it, a file exists. I was there with my finger down.
But did I make it?
Those are two different verbs, and nearly everything I care about lives in the space between them. Take is a moment. Make is a process — and the process did not end when the shutter closed.
The making didn't end at the shutter
What comes off the sensor isn't a photograph. It's a latent thing, flat and undecided, the way an exposed negative isn't yet a picture. Somewhere between that raw record and the image I'd be willing to put my name to, a hundred small decisions get made: how far the shadows fall, how warm the light reads, what the eye is led toward and what it's allowed to ignore. That's where the photograph actually becomes itself. Not at the shutter — there.
The framing was mine. The waiting was mine. The cull — where I throw away the eight near-misses and keep the one — is mine. And the development, the deciding, should be mine too, because that's the part where the photograph stops being a record of what stood in front of me and starts being a statement of what I saw in it.
Photography, for me, is that whole chain. The planning and the surrender to serendipity. The frame. The shutter. The brutal honesty of the cull. The slow work of development. Authorship isn't a single act; it's spread across all of it. Lose any link and you've taken something — but you've made less.
The quiet relocation
Here's what actually worries me, and it isn't what the loud version of this argument says.
The loud version is "AI is bad." That's not my argument, and it's a boring one. Mine is quieter and, I think, more serious: automation moves the moment of authorship out of my hands without my noticing — and it does it precisely by being good.
Press auto. The shadows lift, the color settles, the image resolves into something that looks, often, quite good. Nothing was taken from me that I'd feel as a loss in the moment. There's no alarm; the picture on the screen is pleasing. And that's exactly the trap. The decisions that make a photograph what it is had just been made — by the engine, while I watched — and I'd done nothing but arrive in time to approve them. I became the person who approved the photograph, not the one who made it. The authorship hadn't gone anywhere; it had quietly moved out of my hands and into the software, which handed me back a result to nod at.
It isn't about better
Let me be careful here, because it's easy to slip into the wrong defense.
I'm not claiming my version is better than the machine's. Often it won't be. A model trained on a million images can produce something more balanced, more conventionally pleasing, than my own fumbling toward a look. If the argument were about quality, I'd lose it frequently, and I'd deserve to.
But it isn't about quality. A photograph I didn't make, that happens to be better than one I did — I can admire it. I can't stand behind it. I can't say the one sentence the whole practice is for: I made this. Not "I obtained this." Not "I approved this." Made it. What I'm protecting was never the print's quality. It's whether that sentence is true.
Even if only to me
I know how this sounds, so let me meet the obvious objection head-on: nobody else can tell.
No one looking at the finished image on a wall can see whether I moved the sliders or a machine did. The viewer doesn't care, and shouldn't have to. The "I made this" is not a claim I'm making to anyone. It's a private fact, addressed to myself, and it's worth exactly what I decide it's worth — which, for me, turns out to be a lot.
Because the difference between a practice and an output is precisely this invisible thing. An output is a file that exists. A practice is a relationship — to the craft, to the slow accumulation of judgment, to the version of myself that sees a little better this year than last. If I let the machine make the photographs, I still get the outputs — I just stop having the practice, and the practice was the point. The photographs were always, quietly, a byproduct of the person I was trying to become by making them.
That this matters to no one but me isn't a weakness in the argument. It's the argument.
You don't learn what you don't decide
There's a harder, more practical edge to this, and it's about learning.
I care about photography enough to want to understand it — to stay, as I think of it, on the road of learning what makes a photograph and what doesn't. You can't travel that road by approving. You travel it by deciding, then living with the decision, then seeing next week that it was wrong, and deciding again. Mastery is just that loop, run thousands of times.
Automation severs the loop in two places. The obvious one: if a control quietly does something different every time, depending on what the software thinks it's looking at, there's no stable thing to build intuition about — the ground moves under you. The deeper one is worse. When the software makes the decision, I never even face the question the decision was answering. I don't learn what I'm not asked. The skill I might have built withers before it forms, and I don't feel its absence, because the results keep looking fine. You can be handed competence and remain, yourself, unable — and never know it.
Where the line isn't
I owe an honest concession, because the purist version of this is a fantasy and I won't pretend to it.
I'm not making these photographs by hand. I'm using a computer. A sensor I didn't design recorded the light; an algorithm I didn't write guessed two of every three colors; the instant I open a file, software has already made a first interpretation on my behalf, before I touch anything. The camera made a thousand decisions in the moment of capture. So where, exactly, is the line between a tool I use and a tool that uses me?
There isn't a clean one. There's only a direction. The question was never "did I do every step myself" — that's craft fetishism, and it ends in absurdity. The question is: was the character of this photograph mine, or was it handed to me? Authorship was never purity. It's responsibility for the decisions that matter — the ones that determine what the picture says. A tool that does the indifferent work and leaves those decisions to me extends my hand. A tool that quietly makes those decisions, however well, has taken the picture somewhere I never chose to go. Where exactly the line falls, I couldn't tell you — but I always know which way it's pointing.
The turn
So: I took the photograph. I want, also, to have made it.
Not because the made one is better — it often won't be. Not to prove anything to anyone — no one's asking. I want it because then it's mine, in the only sense that has ever mattered to me: I faced the decisions, I made them, I'm answerable for what came out, and I'm still — frame after frame, year after year — learning how. The making is never finished. That isn't a complaint. It's the part I'd never want handed away.
I took it. Now let me make it.
This is the personal one of three companion pieces. A RAW file is not a photograph is about how light behaves; the folder is the database is about who owns the files. This one is about who makes the picture.