The air in the server room smelled of scorched dust and the ozone tang of a dying uninteruptible power supply, a scent that always reminded me of impending obsolescence. (I recently realized my refrigerator smelled somewhat similar, leading to the unceremonious eviction of three jars of Dijon mustard that had expired during the ).
This specific atmospheric sticktail-a mix of high-voltage electricity and neglected maintenance-was the natural habitat of Sarah, our lead systems architect. To the management team, however, Sarah wasn’t a person so much as a “key person dependency,” or a single point of failure that keeps the CEO awake at night. They looked at her and saw a liability on a resilience report, a bottleneck that needed to be widened until the expertise was spread so thin it became translucent.
01
The Museum of Technological Eras
Sarah’s workspace was a chaotic museum of technological eras, featuring a mechanical keyboard where the “A” and “S” keys had been worn down to smooth, shiny craters. (She claimed the tactile feedback helped her think, though I suspect she just liked the noise it made during long nights of kernel debugging).
The push for