I once convinced myself that I could fix a crumbling relationship by buying a high-end, programmable espresso machine. It sounds ridiculous written out, but at the time, I believed that if I could just automate the morning friction-if I could remove the physical labor of tamping and grinding and steaming-the silence in the kitchen would become peaceful instead of heavy.
My mistake wasn’t just a lapse in emotional judgment; it was a fundamental misunderstanding of how tools work. I spent trying to calibrate the “one-touch” settings, standing over the machine with a digital scale, sweeping fine brown dust off the counter, and becoming, essentially, a manual laborer for a two-thousand-dollar computer.
I was the bridge between the bean hopper and the portafilter, the very thing the machine was marketed to eliminate. I had paid a premium to turn myself into an unpaid technician.
We do this every day with our software, and we’ve been conditioned to think it’s the price of being “tech-savvy.”
Take Joon, for example. I watched him work the other day-a “thread tension” check of a different sort. Joon is a project manager for a firm that handles logistics across three continents. He just finished a call with a supplier in Seoul and a designer in Berlin.
The