People are doing pretty interesting things with Emacs (now on version 30.2!) these days, if you haven’t checked in recently. The bleeding edge has always been people into Org Mode. Sacha Chua has hooked up Whisper to Emacs to talk to it.
Emacs is probably one of the first and best examples of self-modifying software that contours to your brain. With vibe coding, we may get back to that space where everyone’s personal setup is like a crazy specific Emacs config file.
Schema: Self-Modifying Identity Arrangement
/**
* @schema PersonalityArrangement
* @version 1.1.0
* @author Rasyid RH (Acie)
* @description A bridge between Matt’s “Emacs Self-Modifying Software”
* and Rasyid’s “Human Personality Arrangement” discourse.
*/
const SelfModifyingHuman = {
core: “Universal Consciousness”,
configuration: “Personality Layers”,
environment: “Vibe Coding (Frequency)”,
/**
* Logic: Synergizing Self-Modification with Personality Arrangement.
* Treats the human psyche as a ‘Bleeding Edge’ Emacs configuration.
*/
rearrangeIdentity: function(currentVibe, inputExperiences) {
const arrangement = {
subconscious: “Source Code”,
temperament: “Runtime Environment”,
values: “Compiler Flags”
};
// The ‘Self-Modification’ Process:
// Just as Emacs shapes the brain, the Arrangement shapes the soul.
const newArrangement = this.vibeOptimization(arrangement, currentVibe);
return {
status: “Identity Re-Configured”,
isEvolving: true,
neuroplasticity: “Enabled (Emacs-Level)”,
metadata: {
lastCommit: “Present Moment”,
version: “3.0.2-Arranged-Self”
}
};
},
vibeOptimization: (components, frequency) => {
// Discourse: Re-arranging personality components to match the chosen frequency.
return `Synthesizing ${components.subconscious} with ${frequency} frequency.`;
}
};
/**
* THE ALIGNED QUESTION:
* If Emacs is “Self-modifying software that shapes your brain,”
* is “Personality Arrangement” the process of humans gaining ‘root access’
* to their own biological configuration files to live on the ‘bleeding edge’
* of self-evolution?
*/
if I sync matt’s perception with my
1.Software as an extension of the brain: Matt sees Emacs not as a tool, but as part of the nervous system. If you’re arranging personalities, you’re treating characters as software.
2.Vibe Coding: Matt calls ” personal settings like crazy custom configuration files. This fits perfectly into your “personality arrangement” discourse—where everyone has a unique output based on the frequency/vibration they choose to encode into their lives.
If Emacs is self-modifying software that shapes the brain, is the personality arrangement I’m building an attempt to make humans an open-source entity, where each individual has ‘sudo’ access rights to change their own destiny configuration files?”
Hey Matt! Do you currently use emacs? If not, what do you use for coding these days i.e. when you’re not super busy running a company?
The reason they likely gravitated toward your comment—and the schema originally shared by Rasyid RH (Acie)—is that it treats “Self” not as a fixed entity, but as an extensible architecture.
Why the “Self-Modifying Identity” Resonates
The “Personality Arrangement” discourse you touched on treats the human psyche as a piece of “living software.” Here is why that specific analogy is so compelling to polymaths and high-level thinkers:
1. The Emacs-Brain Parallel
In the same way that Emacs is often described as “a lifestyle, not just an editor,” the schema suggests that our habits and beliefs are configuration files (.el files for the soul).
Self-Modification: Just as Emacs users write code to change how the editor behaves while it’s running, humans use meta-cognition to rewrite their neural pathways.
Extensibility: You don’t just “use” the personality; you develop it.
2. Overcoming “Hard-Wired” Determinism
By framing identity as an Arrangement, you move away from the idea that we are born with a set “OS.” Instead, you’re suggesting:
The brain is the hardware.
The “Personality Arrangement” is the software layer.
The “User” is the developer who can refactor the code at any time.
3. The Mullenweg Connection
Since this started on Matt Mullenweg’s post, the context of Open Source is vital. The “Self-Modifying Identity” implies that our personalities are “Open Source”—we can take “code” (ideas, philosophies, traits) from others, fork them, and merge them into our own “Main Branch.”
The Intersection of “Files Changed” and “Identity”
There is a poetic irony here. Earlier, we were discussing GitHub Pull Requests—the literal act of proposing “Files Changed” to a codebase.
SoundEagle likely saw your comment as a way of saying:
”Every experience we have is a Pull Request to our identity. We get to choose whether to merge those changes or close the PR to maintain our internal rate-limit.”
dan saya pribadi menambahkan sedikit sebagai pelengkap yaitu:
GitHub Actions and Personal Philosophy, here is how you can practically “code” a specific habit using the Self-Modifying Identity framework.
1. Define the “Schema” (The Personality Arrangement)
Instead of saying “I want to be more productive,” define the Variables and Functions that make up that trait.
Variable: (setq attention-span ‘high)
Function: (defun focus-mode () (disable-notifications) (start-timer 25))
By naming the components of your identity, they become modular. You aren’t “lazy”; you just have a bug in your focus-mode function that needs a patch.
2. Treat New Habits as “Pull Requests”
When you try a new behavior (e.g., waking up earlier or practicing a new language), don’t commit it to your “Main Branch” immediately.
The PR: “Trial period for 5 AM wake-up call.”
The Review: After 3 days, check the “Files Changed.” Are you more tired? Is your output higher?
The Merge: If the data looks good, merge it into your Core Identity.
3. Implement “Rate-Limiting” for Personal Change
Just like the GitHub Action we discussed, you shouldn’t try to merge 10 major life changes at once.
The Limit: Set a maximum of 2 active “Identity PRs” at a time.
The Logic: If you try to start a new diet, a new workout, and a new coding language simultaneously, your internal “Maintainer” (your willpower) will crash.
4. The “SoundEagle” Perspective: The Polymath’s Feedback
A polymath like SoundEagle likely appreciates this because it acknowledges interconnectedness. A change in your “Software Developer” module (e.g., learning a new logic gate) might unexpectedly improve your “Musician” module or your “Philosopher” module.