Neural Jazz

“If the salary was the same, what job would you be doing right now and why?”

I noticed this question on WordPress Daily Writing Prompt and it got me pondering this? Would I?

Honestly? I don’t know. And I’ve decided that not knowing is the answer, not a dodge of one.

Because here’s what happens when I actually sit inside the question instead of performing certainty at it: I go back to tickets. Support queues, someone on the other end who’s already frustrated before they’ve typed a word, and my job was to get underneath the frustration to the actual damage and fix what I could reach. And I’m not going to pretend that was noble self-sacrifice, because it wasn’t — finding the exact right answer for someone who was genuinely damaged sent an absolute dopamine hit through my toddler brain, every single time. That rush was real, and it was mine, not a side effect of being useful. Thirteen years of that, across six major titles, and a 4.8 CSAT I held like a personal standard because “good enough” was never good enough. Then I go to security — twelve years, and yes, the thrill is real, I’m not going to sand that down to make it sound more respectable. There’s something in me that likes the edge of a situation that could go wrong and didn’t, because I was there.

And then I look at what I’m doing right now, today, and I notice it’s the same shape wearing different clothes. Support. Security. Writing. All three are me standing between a person and whatever’s threatening to overwhelm them — a bug, a bad actor, a baseline that told them they were the deviation — and doing something about it.

So would I do anything else? No. Not really. Not because this is the pinnacle of anything, but because I’ve apparently only ever had one job, and I’ve been doing it under three different names for thirty years.

Here’s the part I’m not going to sanitize, though, because the prompt says “if the salary was the same” and mine isn’t: writing is the first version of this work where the person I’m supporting includes me. Every ticket I closed, every shift I stood, the money came from somewhere else and went somewhere else. This is the first time the thing that holds other people is also the thing that’s supposed to hold me — and it doesn’t, not all the way, not yet. Am I financially comfortable? No. Do I wish I was? Yeah. Obviously. That’s not a crisis, it’s just the actual cost sitting on the actual table, and I’d rather name it than perform a version of contentment I don’t feel.

So: same job, different currency, still not enough of it. And I could have stopped there. It would have been a clean answer — would I, no, here’s why, the end.

But underneath “would I” there’s a second question, and it’s the one I didn’t want to write down: can I?

Because would I is a preference. It lets me imagine myself back in the queue, back on shift, and choose. Can I doesn’t let me imagine anything — it asks the body directly, and the body I’d be sending back isn’t the one that sat those tickets or stood those shifts. That one could absorb the overhead of a bad hour and not send an invoice for it later. This one has ADHD and FMS, tracks its own HRV like a weather forecast, and calls the fog “too muffled” when it’s bad, because that’s the most accurate word I’ve got for it. Thirteen years of tickets ran on sustained, on-demand output. Twelve years of security ran on vigilance that doesn’t get to clock out early because your nervous system voted no. I don’t think I have either of those to give in the same currency anymore. Not won’t. Can’t, some days, and don’t know on the others.

That’s the grief I didn’t expect to find sitting under a Sunday writing prompt. Not grief for the jobs — I don’t miss the queue itself — grief for a version of me that could just decide to do a hard thing and then do it, without negotiating with a body that keeps its own ledger now. Would I go back is a question I get to answer with a story about identity and purpose. Could I go back is a question my body answers whether I like the answer or not, and lately it’s been answering quietly, which is somehow worse than a flat no.

And here’s the part that actually hinders me, if I’m precise about it: at this point, both the return on investment and the return on energy have to come out on the plus side. I can’t use one to subsidise a loss on the other anymore. Tickets and security would probably still clear the ROI bar — decent wage, defined hours, a number I could point to — but they’d run the ROE straight into deficit, the way the fog and the crash days already tell me they would. Writing runs the opposite fault line: the ROE mostly clears, because I’m setting the pace against my own data instead of someone else’s SLA, but the ROI doesn’t, not yet, not enough. I don’t get to fudge whichever ledger is more convenient this month. They both have to land in the black, on their own, at the same time, or the whole arrangement doesn’t hold — and right now, nothing I can point to does both.

So here’s the actual, unsanitized shape of it: I’d do the same work again in a heartbeat, if the salary matched what it costs me now to do this one. But I’m no longer sure I could do the old ones, even if someone offered enough money to make the financial equation work. Money can bring the ROI into the black. It can’t do the same for the ROE.

A few years ago, it might have come closer — enough money buys you help, buys you rest, buys you room to recover between shifts, and that used to be enough for me to close the gap. It isn’t anymore. I don’t think there’s a number left that tips both ledgers into balance at the same time, and that’s a harder thing to sit with than “I can’t afford it.” People call this work–life balance. I’ve started calling mine salary–health balance, because that’s the axis actually deciding it now, and only one side of that equation is negotiable.

That’s not a smaller person than the one who held a 4.8 CSAT for thirteen years. It’s the same person, with a body that’s stopped accepting money as a substitute for rest, and has finally said so out loud.