The Default Settings Nobody Asked For

an empty escalator in a neutral, modern space, no visible faces, slightly cold light.

I spend a lot of time watching people run programs they never installed themselves.

Not in a condescending way. More like a technician watching an old machine grind through its cycles, wondering if anyone has ever once opened the hood. The machine runs. It produces output. Nobody questions whether it was ever the right machine for the job.

That is everyday adult life for most people.

In my first essay, I laid out the operating system I work from — a neurodivergent brain that never received the standard social firmware. No clean installation. Just a custom-built, slightly chaotic setup that forced me to observe human behavior from the outside, like an engineer who was handed a machine without a manual and had to reverse-engineer every single function. What I noticed is that most people are running software that came pre-loaded at birth. And almost nobody ever checks whether it actually serves them.

This essay is about that software. Specifically, the default settings of everyday adult life — the scripts, escalators, and enforcement mechanisms that keep the whole system humming along without anyone ever consciously choosing to press play.

The Escalator Nobody Designed

Here is the life path the machine hands you: go to school, perform well enough to access a slightly better school, graduate into a full-time job, work approximately forty hours a week for forty years, and retire into whatever is left of your body and bank account around age sixty-five.

Nobody sat down and designed this as an optimal system for human flourishing. It was assembled over decades from the needs of an industrial economy that required predictable, interchangeable workers showing up at a factory at the same time every morning. The factory model is largely gone. The scheduling template stayed.

What makes this particular piece of software so durable is not that it works especially well — it is that it comes with the illusion of variation built in. You can pick your industry, your city, your job title, your niche. The cosmetic options are enormous. The underlying architecture is fixed. You are still trading the bulk of your waking hours, your most physically capable years, for a delayed payout that is fragile by design and contingent on variables entirely outside your control.

The mechanical flaw here is not subtle. You front-load the cost and back-load the reward in a system where the payout is not actually guaranteed. Any engineer looking at that design would flag it immediately. Most people never even open the schematic.

And the escalator does not just move you forward — it moves you forward at a fixed speed with no controls available to the rider. You cannot slow it down when your circumstances change. You cannot speed it up when the timeline stops making sense. You simply ride it, and the expectation is that you look grateful for the ride.

The Performance of Politeness

Every functional society needs social lubrication. I understand this. Without it, human interactions generate too much friction, and high-friction systems are inefficient. So a layer of scripted, low-cost social exchange evolved to keep the gears from grinding — pleasantries, small talk, performative enthusiasm, and the elaborate theater of office communication.

What I find interesting is not that these scripts exist. It is how completely unconscious most people are that they are running them.

How are you? is not a question. It is a ping. The expected response is not an honest status report — it is a confirmation that your node is online and operating within acceptable parameters. Fine, thanks, you? completes the handshake. The exchange is over. No actual data was transferred.

From the outside, this is fascinating. From the inside, when your brain does not execute these scripts natively, it is exhausting in a way that is genuinely hard to explain. I have to manually locate and run each social program in real time while simultaneously managing the rest of the interaction. The cognitive overhead is significant. What other people execute automatically, I perform deliberately.

But here is what that overhead revealed to me: most social scripts are not about connection. They are about friction reduction. They signal that you are a cooperative node in the network — non-threatening, compliant, predictable. The actual human being running the script is largely irrelevant to the exchange.

The system is not designed to know you. It is designed to process you.

The Friction of Enforcement

You might wonder how a system with no central authority and no enforcement mechanism keeps hundreds of millions of people running the same default settings. The answer is that it does not need overt enforcement. It outsources that function to the participants themselves.

Deviation from the default path generates friction automatically. Step off the standard escalator — leave the stable job, opt out of the homeownership timeline, refuse the promotions, restructure your schedule in a way that optimizes for your actual life rather than productivity theater — and watch what happens. The people closest to you will express concern. Well-meaning concern. Concerned concern. The kind of concern that, when you examine it carefully, is structurally identical to social pressure wearing a polite mask.

The mechanism is elegant, if you can appreciate it from a distance. There is no authority figure issuing warnings. The friction is generated peer-to-peer, automatically, by people running default settings who experience your deviation as an implicit critique of their own choices. They are not necessarily being malicious. They are being reactive. Your exit from the escalator raises a question they do not want to sit with: what if I could have gotten off too?

That question is uncomfortable enough that the easiest resolution is to make your exit look like a mistake. So the concern arrives. The cautionary stories get told. The statistics get cited. The well-meaning people in your life become, without realizing it, unpaid enforcement agents for a system that never asked their permission either.

This is worth sitting with for a moment, because it reframes something most people experience as personal — the pushback from family, the skepticism from colleagues, the ambient noise of other people’s anxiety projected onto your decisions. None of it is actually about you. It is a system response. You triggered an error-correction subroutine, and the subroutine is running exactly as designed. Understanding that does not make the friction disappear. But it does change what the friction means. It stops being evidence that you are wrong and starts being confirmation that the system noticed you left.

Engineers call this a self-correcting system. The correction mechanism here is social discomfort, judgment, and the low-grade hum of collective disapproval. No violence required. No authority required. Just the reliable, ambient weight of other people’s unexamined choices pressing against yours.

Securing Root Access

I am not interested in burning the machine down. That is not the point of any of this.

The machine serves real functions. Some of the defaults exist for legitimate reasons. Stability, cooperation, shared infrastructure — these require some degree of standardized behavior. I am not arguing for a world where everyone abandons every social script and lives entirely on their own terms with zero regard for anyone else. That is just a different kind of dysfunction.

What I am arguing for is something more surgical: root access to your own operating system.

Root access means you get to audit every script before it runs. You examine the default settings and ask, with genuine skepticism, whether each one was installed intentionally or just inherited. Some of them survive the audit. The forty-hour workweek structure might actually suit you. Some social scripts might be worth running because they genuinely serve the relationships you want. Fine. Keep them. But keep them because you chose them after examination, not because they came pre-loaded and you never thought to check.

What root access actually looks like in practice is less dramatic than it sounds. It looks like questioning the career path before committing another decade to it. It looks like noticing when you are performing an emotion you do not feel because the social script requires it. It looks like recognizing that the friction other people generate around your choices is a feature of their system, not a verdict on yours.

The goal is not a perfectly optimized, friction-free life. That does not exist. The goal is to stop running programs you never consciously chose and start building a framework that is actually calibrated to your specific conditions, constraints, and what you are trying to do here.

Once you can see the engine clearly — the escalator, the scripts, the self-correcting friction — you cannot unsee it. Playing along in complete ignorance stops being an option.