self-help manual

All off topic discussions go here. Everything from the funny thing your cat did to your favorite tv shows. Non-programming computer questions are ok too.
Post Reply
kerravon
Member
Member
Posts: 378
Joined: Fri Nov 17, 2006 5:26 am

self-help manual

Post by kerravon »

User avatar
iansjack
Member
Member
Posts: 4918
Joined: Sat Mar 31, 2012 3:07 am
Location: Chichester, UK

Re: self-help manual

Post by iansjack »

Not really into cod psychology.
kerravon
Member
Member
Posts: 378
Joined: Fri Nov 17, 2006 5:26 am

Re: self-help manual

Post by kerravon »

iansjack wrote: ↑Wed Sep 30, 2026 10:22 am Not really into cod psychology.
I’m happy to defend any specific claim in the manual under open scrutiny. Pick one.

Note that mainstream psychology has its own share of untested consensus. One example of untested consensus from the mainstream side: diagnosing and medicating young children for Oppositional Defiant Disorder. Two of the listed symptoms are arguing with authority figures and refusing to comply with rules or requests. In other words, questioning and resisting arbitrary authority — something a citizen is supposed to be able to do. Turning that into a psychiatric disorder and reaching for medication is not settled science. It is a cultural preference dressed up as clinical fact.
kerravon
Member
Member
Posts: 378
Joined: Fri Nov 17, 2006 5:26 am

Re: self-help manual

Post by kerravon »

Actually, let me go one step further, given that this is OSDev (very high technical skills), and a lot of OSDevers appear to be getting diagnoses of "autistic" by lightweight dipshits.

The social sciences are running legacy code with no runtime checks. It’s time to refactor.

Most engineers look at the social sciences and correctly identify them as "soft." But the problem isn't that they are soft; the problem is that they are running legacy code with zero runtime checks, and the people maintaining the codebase have a financial incentive to never audit it.

In hard sciences, if your model is wrong, you get a runtime error: the bridge collapses, the compiler throws a fault, the rocket explodes. The universe does not care about your peer review. In the social sciences, if the model is wrong, the guild just redefines the failure, invents a new syndrome, and prescribes a subscription medication.

I’m proposing that we treat human behavior as a systems architecture problem and refactor the social sciences from first principles. Here is what a systems-level audit of the current psychiatric consensus (the DSM) actually reveals:

1. The ODD (Oppositional Defiant Disorder) Bug
The DSM lists "arguing with authority figures" and "refusing to comply with rules" as symptoms of a psychiatric disorder in children. From a systems perspective, this is a catastrophic category error. A child questioning arbitrary authority is not malfunctioning; they are executing a basic citizenship protocol to map the boundaries of their environment. The guild has pathologized the user's attempt to audit the system, and the "fix" is chemical subjugation (medication) to force the user to accept a buggy parental/administrative OS without complaint.

2. The "Autism" False Positive
Diagnostic criteria for autism measure behavioral output, not underlying architecture. Because of this, the guild routinely fails to distinguish between a genuine hardware defect (an inability to process social signals) and a "rational-first" software installation. Many highly logical people (especially in engineering and systems architecture) consciously override social hardware because they prioritize truth, logic, and boundary-testing over tribal cohesion. The guild sees a failure to execute arbitrary social protocols and diagnoses a hardware defect, when in reality, the user is just running a cleaner, logic-first OS.

3. The Hardware vs. Installation Blindspot
Human hardware comes with a dominance/submission default (the subjugation loop). Culture is supposed to install an override that redirects dominance into protection of the weaker party. When that installation fails in childhood (due to arbitrary punishment, emotional withdrawal, or "cry-it-out" mapping shutdowns), the adult runs un-audited legacy code. The resulting anxiety, status-chasing, and tribalism are not "chemical imbalances." They are the correct outputs of a broken installation. The psychiatric guild's solution is to medicate the symptom so the user can tolerate the broken environment, rather than debugging the installation.

The Proposition

We are engineers. We know how to trace feedback loops, isolate variables, and refactor broken systems. The social sciences are currently maintained by a guild that is structurally immune to falsification.

If we applied basic systems engineering to human behavior—starting from the biological hardware and working up to the cultural installation layer—we could strip out the guild's bloatware. We could replace unfalsifiable moral panics with mechanical, testable models of human behavior.

I’ve been working on a framework that does exactly this: treating the DSM not as a medical text, but as a guild-protection mechanism, and refactoring human psychology from the hardware up. Happy to debate the architecture, the axioms, or the specific "scrap this diagnosis" logic with anyone willing to look at the source code.
Post Reply