Frank
1.
The first thing I figured out, somewhere around year eight of my career, was that I was not slow, lazy or difficult. I was processing every single thing in the room simultaneously, all the time, and nobody had told me that wasn’t normal. I thought everyone did that. I thought everyone left a two-hour meeting feeling like they’d spent the last 120 minutes with their hand on an electric fence.
They don’t, I do. That’s a different OS.
2.
Here’s what AuDHD actually looks like in an enterprise IT environment, from the inside:
You can hyper focus on an Exchange PowerShell scripts for four straight hours without eating, without moving, without noticing that the building got quiet because everyone else went to lunch. You’ll find the problem. You’ll fix the problem. You will have documented seventeen related observations along the way that nobody asked for.
Then your boss sends a Teams message asking for a status update on a completely different ticket, and your brain genuinely cannot locate that ticket in real-time because the context switch is physical. It feels like being asked to parallel park while someone’s shouting multiplication tables at you.
From the outside, that looks like inconsistency. From the inside, it’s just how the processor handles interrupt requests.
3.
I’ve spent 29 years building a career around systems that have rules. Active Directory has rules. Exchange has rules. DNS has rules. You break a rule, you get an error. The error tells you something. You fix it.
I am extremely good at that world. Always have been. I can look at a mail flow diagram and immediately see where the logic breaks. I can feel when a configuration is wrong before I can articulate why.
What I cannot do, without significant effort, is navigate a meeting where the rules are unwritten, the agenda is vague, and three people are having a side conversation while the main presenter is still talking. That environment doesn’t generate error codes. It generates social fallout that I don’t detect until three days later when someone’s weird to me in the hallway and I have absolutely no idea what I did.
Two different environments. Two completely different failure modes. Same brain.
4.
The corporate IT world runs on a rhythm that I’ve never naturally matched. Stand-up at 9. Email response within the hour. Available on Teams. Visible in the office. Sociable at the right moments. Focused at the right moments. Flexible when asked. Consistent by default.
I’ve spent most of my adult life brute-forcing that rhythm. Masking, even though I didn’t have a word for it until I was 54 years old. I built systems to compensate. To-do lists that would frighten a normal person. Calendar reminders for things most people just remember. Scripts to automate the repetitive stuff so my brain didn’t have to carry it. I thought I was just being organized. Turns out I was building accessibility tools for myself.
5.
The thing nobody tells you about late diagnosis is that it doesn’t fix anything backward.
Getting that AuDHD label at 54 explained a lot. The meltdowns I called frustration. The burnout cycles I called laziness. The social exhaustion I called being an introvert. The hyper focus I called being good at my job. The rigidity I called having standards.
But explaining something isn’t the same as changing it. I still have to sit in meetings. I still have to manage the context switches. I still have to regulate a nervous system that treats a misconfigured distribution list and a sudden loud noise in the hallway as equivalent threat levels. Knowing the name of the operating system doesn’t patch its vulnerabilities.
The Part That Actually Matters at Work
6.
What changed, practically, was that I stopped trying to fix the wrong thing.
For years I was trying to be a better version of the person everyone expected me to be. More responsive. More available. More flexible. More patient in situations where patience required me to suppress every instinct I have.
When I finally understood what I was working with, I started building around it instead of against it. I chunk deep technical work into blocks where I won’t be interrupted. I use written communication by default because my brain processes text better than verbal conversation in real-time. I keep detailed notes not because I’m thorough but because my working memory is genuinely unreliable under stress and I learned that the hard way at a very inconvenient moment during a past job interview.
I think long term but operate in small experiments. That’s not a productivity philosophy I read somewhere. That’s just how I actually function, and it took me most of my career to stop apologizing for it.
7.
Here’s what the hardware analogy actually means, practically:
Two systems running on identical hardware can produce wildly different results depending on the OS. One might be more efficient in single-threaded tasks. One might handle parallel processing differently. One might require more RAM for routine operations. Neither is broken. They’re just optimized differently, and the problems start when you try to run software designed for one on the other and then wonder why the output looks wrong.
Corporate environments are largely designed by and for neurotypical people. The communication norms, the meeting structures, the performance review language, the concept of “executive presence,” all of it assumes a particular type of processor. When your processor works differently, you’re not failing to meet the standard. You’re running incompatible software on your architecture, and the system keeps throwing exceptions that look like personal failures.
They aren’t.
8.
I’ve been a Computer Technician, Systems Analyst & Systems Engineer for nearly 18 years at the same organization. I’m genuinely good at my job. I’ve built things that work, solved problems that stumped people with more formal training, and kept systems running that a lot of people depend on.
I’ve also been written off in meetings because I was quiet. I’ve been passed over for things because I didn’t perform enthusiasm the right way. I’ve burned out completely, more than once, and come back and kept going because the alternative was worse. I’ve had days where fixing a complex PowerShell issue was the easiest thing I did, and sending one email to a colleague required thirty minutes of mental preparation.
Both of those things are true at the same time. That’s what this is.
The OS isn’t inferior. It just wasn’t documented, and nobody handed me the manual until most of the game was already played.
