I stopped believing my own linen loss reports
I once ruined an entire season’s worth of provenance data for a small Roman archaeological site near Arles by trusting a database I hadn’t properly audited. It was a excavation, and I was tasked with cataloging every fragment of amphorae and glass that came out of the trench, using a MacBook Pro, a dusty copy of FileMaker Pro, and a set of handwritten field notes.
I assumed that the absence of a digital record for a specific crate meant the crate itself was empty or already processed. I didn’t check the physical storage locker because the screen told me the job was done, and by the time I realized that 417 iridescent glass fragments had been left to gather dust in a mislabeled corner, the site had been backfilled and the grant money had run dry.
Just last week, I caught myself repeating a version of this mistake in my own digital life, spending four hours updating a suite of archaeological rendering software that I haven’t actually opened in . The progress bars and the version numbers-v4.2.1, v4.2.2, v4.3.0-provided a sense of productivity that was entirely disconnected
