My boss told me to "Wait for Jim" to fix a multi-million pound machine. I realized I'm just a rented component.
I’m 41. I operate a Gietz ROFO 870 foiling machine in a factory. It’s a massive, high-pressure system. If I screw up the tension, we lose thousands of pounds in paper and foil.
Last week, the motor started dragging. I reported the issue. The top manager and the mechanic looked at it, shrugged, and said: "When Jim comes back from retirement in May, he'll fix it."
Jim is the only guy who knows the machine better than me. Until he decides to show up, I’m expected to just "run it slow" and deal with the stress.
It hit me: I am a rented component. If I break, or if Jim doesn't come back, or if the factory closes, I have nothing.
I look at the developers on this sub, and I see the same thing. You make £80k-£120k, you have a nice chair, but you’re just a factory worker on a digital assembly line. You’re fixing "Legacy Debt" created by some "Jim" who left the company three years ago. You’re "highly paid," but you own zero percent of the code you write. You are just as replaceable as the agency worker who walked off my floor yesterday because he refused to pack boxes for £12.25/hr.
I cycle 3.7 miles home in the rain at 5 a.m. because I refused to accept this. I spent the last two years taking the logic I use to run this Gietz and applying it to a Notion-based CI/CD pipeline for my own digital assets. No "Busy Fool" behavior. No wasted motion. Just raw production.
I’m not a "coder" anymore. I’m a Systems Operator.
I’ve built a protocol called The Vault to manage my build-out without burning out after a 12-hour shift. It uses a strict "Max 3 Cards" rule to kill "Busy Fool" behavior and forces me to only focus on high-signal output.
I'm curious: for the developers here who are actually trying to escape the digital assembly line, how are you managing your side-project architecture without turning it into a second shift of donkey work? Have you built a better protocol, or are you just grinding until you break?