12.17 — The survivor’s psyche: “enemies”, “narcissism”, “hell”, “survival”, and how it bubbles up into the code#

Ocarina’s Holy Book author uses strong words: enemies, narcissism, hell on earth, survival. These words aren’t stylistic flourishes. They’re the precise descriptors of an experience lived by a whole cohort that went through the 2000s underground internet described in 16-underground-internet-2000s.md. This page explains why these words are accurate, what this lived experience produces on the psyche, and how these psychological adaptations imprint deeply into the way one programs, architects, always stays up to date.

1. “Survival” in the literal sense#

When an average consultant says “I survive my deadlines”, he’s talking about fatigue.

When Ocarina’s author writes survival, he describes:

• Having seen peers die.
• Having seen peers sentenced to heavy prison terms.
• Having seen peers psychically destroyed, disappeared.
• Having himself been in the crosshairs at some point.

In this frame, survival takes its proper meaning: still being here, in a state to produce, not in prison, not psychically broken, still independent.

Statistically, in the 1995-2010 hacker cohort, being still here productively in 2026 is the exception, not the rule.

2. “Hell on earth”#

This superposition produces an experience quality that isn’t found in ordinary civilian life — hence hell on earth.

3. “Narcissism”#

Ocarina’s author identifies narcissism as a recurring trait of the adversaries he met professionally.
It’s neither a cheap insult nor a gratuitous accusation — it’s a clinical observation.

Clinical definition#

Pathological narcissism (NPD — Narcissistic Personality Disorder, DSM-5) is characterized by:

1. Feeling of grandiosity without corresponding achievements.
2. Fantasies of unlimited success, power, brilliance.
3. Belief in being special, understandable only by high-level peers.
4. Excessive need for admiration.
5. Sense of entitlement: expecting favorable treatment without justification.
6. Exploitation of interpersonal relationships.
7. Lack of empathy.
8. Envy of others, or belief that others envy oneself.
9. Arrogant or contemptuous behaviors.

Why the narcissist is the natural enemy of the underground creator#

The narcissist in the professional world#

Typical case lived by an underground technician trying to reintegrate:

1. He joins a company.
2. The narcissist doesn’t understand his work but has to benefit from it for his careerism.
3. He self-attributes successes publicly.
4. He attacks, sabotages the technician as soon as the latter tries to explain what he does — because explaining would reveal the real contribution, hence threaten the self-attribution. He also does it out of pure hate.
5. The technician eventually leaves, either fired or pushed to the breaking point.
6. The narcissist tells HR an alternative story, sometimes public, where the technician is the problem.

This pattern is structural, not anecdotal. Any veteran technician of the underground scene has lived several iterations of this scenario. It’s this repetition that justifies the Holy Book’s tone when it says “slipologues”. They are, in precise diagnostic terms, the narcissists infesting the industry. It’s a declaration of war.

Named directly#

The Holy Book is explicit on this point.

1. The sovereign creator has, by construction, consciousness of his value (otherwise he wouldn’t have the strength to create solo, MIT, hierarchy-less).
2. The narcissist is, by construction, an impostor.
3. These two postures are incompatible in the same team. One detects the other and sees it as threat.
4. The narcissist seeks to neutralize the creator. The creator seeks to flee (or to destroy) the narcissist.

4. “Eyes everywhere”#

Operational origin#

On an underground IRC server:

• The op (channel admin) has access to logs.
• If Anonymous show up to coordinate an operation (DDoS, doxing, hack), the op has to know.
• If the operation is conducted, and later hits the press, authorities will trace back to the servers.
• The op who didn’t alert ends up legally accomplice (even if he did nothing technically).

To survive as an op, you have to have eyes everywhere.

The generalization: hyper-vigilance as lifestyle#

Once acquired, this surveillance doesn’t switch off. The veteran keeps:

• Reading between the lines of received messages.
• Systematically cross-referencing each new piece of info.
• Maintaining a mental map of relationships among actors.
• Detecting weak signals (tone change, sudden absence, contradictions).
• Evaluating the cost of each interaction before entering it.

Hence the psychological cost: you no longer know how to turn it off.

5. How these adaptations bubble up into the code#

The survivor’s psyche does NOT stay in the personal sphere — it imprints into the software architecture he produces.

Audit-reflex#

If I can’t audit the thing in an afternoon, it’s too much.

• 1 runtime dependency only.
• MIT + end-to-end readable code.
• No plugins: every dependency adds blind spots (see ../11-independence/02-auditability.md).
• No SaaS: every service adds an uncontrolled surface.

Trust-no-one at the code level#

• Mypy strict: the compiler checks everything — we don’t trust the runtime.
• Result[T] everywhere: no silent exception, every failure is explicit and carried as value.
• Probes before assertion (see 15-typing-ai-rl-probes.md): we observe before declaring.
• No silent retry without log: every retry must leave a trace.

Compartmentalization#

• Hexagonal architecture in 02-ocarina/ (railway → custom_types → dsl → infra → opinionated). Each layer is isolated.
• Project adapters: projects compose Ocarina.
• Typed POMs: clean interfaces between intent (the test) and DOM (the implementation).

Own what you can own#

• GitHub only because you need a host: the code is built to be movable to GitLab, Codeberg, self-hosted, in 1 day.
• No Cypress Dashboard: artifacts (screenshots, logs, videos) are local.
• Etc.

Always stay up to date#

• Ocarina supports Python 3.14+ as soon as it ships (code uses PEP 695, which is recent).
• Rigid version pinning to mitigate Supply Chain Attack risks.
• Adoption of pnpm 11 immediately due to new security patches.

This last adaptation is crucial and often misunderstood. Always update isn’t hype. It’s a security reflex. The author knows that any version left lying around ends up with a CVE discovered, exploited, and used against him if he doesn’t patch.

Code as testament#

The surviving creator writes code that has to outlive himself:

• MIT: anyone can fork.
• Small: anyone can understand.
• Well typed: anyone can verify it through static analysis.
• Documented for AI: any agent can maintain it.

It’s the exact opposite of the corporate philosophy (lock-in, stack trade secrets, maximized dependency). It’s explicitly a continuity strategy beyond the author.

6. Operational paranoia vs clinical paranoia#

We speak of operational paranoia, not clinical:

Ocarina’s creator is in the first category. His code is rigorous.

7. Why these adaptations have economic value#

1. AI grows the attack surface.
2. Fraud costs explode.
3. Regulations tighten audits.

In this context, the survivor’s psychological adaptations become competitive advantages:

• Audit-reflex.
• Zero trust.
• Constantly up to date.

See 08-ocarina-in-testing-industry.md

8. Closing word#

All the work around Ocarina isn’t only technical production — it’s also transmission.

The author writes to:

• Document what he has learned, so that the next generations don’t have to relearn it through suffering.
• Validate publicly (MIT, in French + English, accessibly) a posture that hasn’t had a place in institutions.
• Emerge from operational solitude: make his world readable to a broader audience.
• Bequeath an object that will outlive its author, as YTCracker leaves Nerdlife, as Yung Innanet leaves true colors, as Sys64738 left Zone-H.

It’s an act of collective reparation.

9. Connections with the rest of the primer#

• 07-underlying-movement.md — the brotherhood reconstituted through Research.
• 12-dhh-paul-graham-haters-mean.md — Mean People Fail and the narcissist in startups.
• 16-underground-internet-2000s.md — the operational context.