Someone handed me an instruction manual once. Literal paper, stapled in the corner, twelve pages long. I read every word. I still did it wrong, and I still couldn’t explain why.
That’s the part that doesn’t make the LinkedIn posts about “neurodivergent superpowers.” Not the interesting stuff. Not the hyperfocus that lets you disassemble a problem at two in the morning and rebuild it into something elegant before sunrise. The other part. The part where you followed every visible rule and still ended up on the wrong side of an invisible one.
AuDHD. Autism and ADHD living in the same brain, which is either a cruel joke or a fascinating engineering decision depending on the day. The autism wants systems, patterns, consistency. The ADHD lights those systems on fire and finds the flames genuinely beautiful. You don’t get to pick which one shows up to a given meeting.
Here’s what I’ve never seen written down anywhere: it’s not primarily a productivity problem. It’s a translation problem.
Every institution, every workplace, every social contract was written by people who share a common operating system. They didn’t conspire to exclude you. They just wrote the documentation for themselves. Not only that, but they didn’t notice the assumptions baked into every line, the same way a fish doesn’t notice water. Unwritten rules, implied schedules, “reading the room,” knowing when a meeting is actually over even though nobody said so. These things feel obvious to people who were always running the same OS.
To me, they feel like trying to parse YAML with a missing schema. The file looks fine. The syntax checks out. And then something fails anyway at runtime because there was a context I didn’t have, a convention nobody wrote down because everyone else already knew it. I once watched a deployment pipeline fail for three hours because someone put a smart quote in a YAML file. One character. Invisible to the naked eye. Everything downstream, broken. That’s not an analogy. That’s just Tuesday, twice.
The frustration isn’t confusion, exactly. It’s more like arriving late to a conversation that started before you got there, every time, in every room. You’re not slow or stupid; you’re simply working with a different parsing engine, and no one gave you the proper input format.
What makes this special brand of exhaustion so sneaky is that you can become a black-belt master at faking functionality. Masking, clinically speaking. In everyday terms: acting “normal” with such precision that people stop seeing the glitch in the matrix. It’s not a free superpower, it comes with a price tag. Every conversation is like running subtitles in your head, every meeting is a juggling act between keeping your face on-brand and following the plot, and every emotion has to be translated into something socially edible. That’s mental RAM burning nonstop. Forever. You can’t close the browser, it’s part of the operating system.
And here’s the thing nobody talks about honestly: the masking usually works. That’s almost the worst part. You get good enough at it that people are surprised when you eventually tell them, or when the mask slips, or when you hit a wall and suddenly can’t. “But you seem so normal.” Yeah. I’ve been practicing since I was seven. I had to. The alternative was worse.
What changed for me wasn’t a diagnosis, though that helped clarify the map. What changed was understanding that the exhaustion I’d been writing off as personal weakness was actually structural. I wasn’t tired because I was broken. I was tired because I’d been running a translation layer between my actual brain and the expected interface for thirty-plus years without ever naming what it was. Naming it doesn’t fix it. But it stops you from blaming yourself for the wrong things.
The satisfaction, when it comes, is real. Hyperfocus is genuinely one of the stranger gifts I’ve had access to. When something catches in that particular way, nothing else exists. Problems that would take other people days of grinding get solved in one long overnight session fueled by coffee and some obscure momentum that I can’t manufacture on demand and can’t fully explain. The pattern recognition is real. The ability to find a structural flaw in a system that looks fine on the surface, that’s real too. I don’t say that to brag. I say it because there’s a tendency in these conversations to either over-romanticize the whole thing or treat it purely as deficit. It’s neither. It’s a different configuration, and like any configuration, it has tradeoffs.
The identity part is the part that takes the longest. Because for most of your life, the story you’ve been told about yourself, the story you’ve absorbed, is one of inconsistency. Unreliable. Forgetful. “Could do better if he applied himself.” “So smart but doesn’t try.” “Spacey.” “Difficult.” The labels stick, not because they’re accurate, but because they come from people who had authority and no framework for what they were actually seeing. You internalize them before you’re old enough to audit them.
Unlearning that is not fast. It’s not clean. It doesn’t happen in a weekend workshop. You have to go back through your own history and re-examine things you thought were character flaws and realize that some of them were load-bearing walls in someone else’s convenience. Turns out “difficult” sometimes means “requires explanation” and “explanation felt like too much work.”
The systems I build now are built for my actual brain, not for the brain I was supposed to have. I over-document. I build external structure because my internal structure is unreliable on good days. I schedule things that other people handle intuitively, not because I can’t function without a schedule, but because a schedule means I’m not spending cognitive load on “what am I supposed to be doing right now.” I protect the conditions under which I actually do good work, because I finally stopped being embarrassed that those conditions are different from what the open office floor plan was designed for.
None of that is a superpower. It’s just maintenance. It’s just knowing the machine well enough to stop fighting its actual tolerances.
The original instructions were clearly meant for someone else, so I’ve been crafting my own. They’re longer, clumsier, and look like they were attacked by a pen-wielding squirrel. But for the first time ever, they’re actually accurate.