About twenty percent of people score high on sensory processing sensitivity — the trait psychologist Elaine Aron spent her career mapping. The stereotype is fragility. The research says something more interesting: high-SPS people process stimuli more deeply, notice more context, and are disproportionately affected by their environments, for better and worse.
I'm one of them, and I write software for a living. Here is what that combination actually looks like.
Depth of processing is a code review superpower
The same wiring that makes an open-plan office exhausting makes a subtle race condition hard to un-see. Deep processing means I don't skim — a pull request gets read the way an editor reads a manuscript. The cost is speed on trivial tasks. The benefit is that the class of bug that survives three reviewers tends not to survive a fourth who literally cannot skim.
Environments are not neutral
For most engineers, a noisy Slack culture is an annoyance. For a highly sensitive one, it's a tax on every working hour. I've learned to treat my environment as part of my toolchain: notifications batched, deep work scheduled against meetings, and a permanent bias toward written, async communication — which, conveniently, is also just better engineering practice.
The reframe
The industry optimizes for people who thrive on interruption and ambiguity tolerance. It underprices people who notice everything. If you recognize yourself in this: the trait is not the problem. The unexamined environment is. Build yours deliberately, the way you'd design any other system with known load characteristics.