The Arrogance of the Manual Ripple
I once spent trying to make a river look like it wasn’t dying. I was working on a series of maps for Ethan J.D., a wildlife corridor planner who spends his months tracking the movement of cougars and elk through the increasingly fragmented scrublands of the Pacific Northwest. He needed the visual data to look pristine for a board of county commissioners who generally preferred asphalt to apex predators.
My mistake was not the time I spent, but the arrogance of my method. I had convinced myself that if I didn’t manually trace every ripple in the water, every shadow cast by the overhanging basalt, the final image would lack “soul.”
Saving File: River_Map_Final_v4.psd (12GB)
99%
“The little blue line pulsated with a kind of rhythmic insolence.”
The metaphor for the old way of working: the agonizing pause where the human waits for the machine to catch up.
By the , my wrist was a knot of fire. I had a 12GB file open, and I was using a healing brush to remove a stray soda can from the foreground. I hit save. The progress bar crawled across the screen and stopped at 99%. It stayed there. I watched the little blue line pulsate with a kind of rhythmic insolence.
I sat there for , staring at