The Day I Stopped Refreshing My Slack Notifications
It was a Tuesday in March 2024, and I had been checking Slack every four minutes for three weeks. Not because anyone was messaging me — they weren't — but because the silence itself had become a kind of information I couldn't stop trying to decode. Was the quiet good? Was it administrative? Was it the particular quiet of people who already know something you don't?
I had been at the company for fifteen years. I started when the codebase was small enough that I had personally written maybe a third of it. By the time I left, that fraction was cosmically small, but I still knew where the bodies were buried — the legacy authentication module nobody touched, the scheduler that worked for reasons nobody fully remembered, the comments I'd written in 2013 that were still there, slightly embarrassing, preserved like insects in amber. That institutional knowledge had always felt like ballast. It turned out to be the thing I'd confused for job security.
The meeting invite came on a Wednesday, no agenda, from an HR partner I'd never spoken to. Everyone in the industry knows what that means. You know before you know. I spent the night before doing what engineers do when they're scared: I made lists, I ran scenarios, I calculated runway in a spreadsheet with tabs. Preparing for a negotiation that wasn't going to be a negotiation.
What I didn't prepare for was how specific the language would be. They didn't say "restructuring" or "market conditions." They said the team's work was being "transitioned to an AI-assisted workflow," and that my role, specifically, had been "identified for sunset." Sunset. As if my fifteen years were a pleasant end to a day rather than an interruption in the middle of one.
I want to be precise about what happened to me emotionally, because imprecision is how these experiences get flattened into either tragedy or inspiration, and mine was neither. What I felt first was not grief. It was a kind of cognitive dissonance so acute it was almost physical — the gap between how competent I knew I was and how disposable I had apparently become. I had shipped production code two weeks before that conversation. I had done a performance review the month before that had gone well. The ground doesn't feel like it's moving until it isn't ground anymore.
The grief came later, slower. It came in the form of realizing I didn't know who I was outside of being someone who was good at this particular thing. Software engineering had been the stable fact around which everything else in my life was organized. My salary, obviously. But also my self-concept, my friendships, my daily structure, the way I introduced myself at parties. When someone asks "what do you do" and the answer has been the same for fifteen years, you stop noticing how much of your identity is just an answer to that question.
I spent the first month trying to find the version of this story where I had done something wrong, because that version would have been more actionable. If I had failed, I could improve. But I hadn't failed. The technology had simply moved into the space I occupied. That's a harder thing to metabolize, because it doesn't give you a correction to make. It just gives you a new situation to be in.
What I eventually found — and this took longer than I'd like to admit — was that the financial shock and the identity shock needed to be separated and addressed individually. I had savings, which bought me time, but I knew that most of the engineers I'd worked alongside over the years didn't have three months of runway, let alone the emotional bandwidth to job-hunt while also renegotiating who they were. The financial precarity was the thing that compressed every other problem. When you're terrified about rent, you can't think clearly about what you actually want to do next. You just take the first thing.
I stopped refreshing Slack about six weeks after the call. Not because I made a decision to stop, but because I finally accepted that there would be no message. The channel had just ended. What replaced the compulsive checking was something quieter and stranger — a kind of attention to what I actually wanted to build, now that the structure I'd been building inside of was gone.
I can't claim that clarity was a gift. It wasn't. It was a byproduct of having no other choice. But I did eventually build something with it: Clankers, an income protection product for workers displaced by automation, which I run today. I mention it only to account for why I have opinions about this particular subject. I have been in the meeting with no agenda. I know exactly how long it lasts, and what the air feels like afterward.
PROTECT YOUR INCOME NOW
If AI automation threatens your job, preparation is the only honest answer: know your risk, build a runway, and reskill before you have to. The Clankers 90-day programme structures exactly that — free, which is exactly why today is the right time to start.
Start the 90-Day Programme — Free →GET THE CLANKERS BRIEF — FREE
One email every Monday: the week's AI displacement moves that matter, and what to do about them. No spam. Unsubscribe anytime.