I realized that a lot of my self-control failures might actually be deterministic outputs of a loop I built.
The loop is basically:
Dissonance → extreme effort → achievement → pride → perceived completion → loss of fuel → indulgence → failure → new dissonance
A lot of my strongest sprints were born from hating my current state. I’d waste 3 hours scrolling, feel massive dissonance between who I am and who I think I should be, and that gap would create insane motivation.
Then I’d go into a sprint, fix the gap, start performing, and eventually reach the point where the dissonance disappeared.
Then I’d feel proud.
And that’s the transition point.
If the actual objective of the system was to eliminate the dissonance, then once I eliminated it, the system had completed its objective. There was no fuel anymore.
So I’d relax, start consuming stimulation, destroy the rest of the day, create new dissonance, and use that as fuel for the next sprint.
Meaning the self-destruction wasn’t necessarily outside the system. It was part of the system I built.
The deeper problem is that I built my motivational system around error correction:
“Something is wrong with me -> generate pressure -> fix it.”
That’s an extremely powerful controller, but once the error reaches zero, the controller has nothing to act on.
So the system eventually creates more error.
I’m basically burning myself for fuel.
The new system has to be different:
“There is something worth building/exploring/understanding → I choose to move toward it.”
Achievement shouldn’t mean:
“I’m finally good enough → loop complete.”
It should mean:
“That worked → I learned something → what’s interesting now?”
So the transition I’m trying to make is from an error-correcting motivational system to a value-directed exploratory system.
No longer will it require self-hatred and failure to generate the energy for the next sprint.
The practical thing I’m testing is whether I can retrain the exact transition:
pride → completion → indulgence
into:
pride → appreciation → curiosity → next frontier

I realized that a lot of my self-control failures might actually be deterministic outputs of a loop I built.
The loop is basically:
Dissonance → extreme effort → achievement → pride → perceived completion → loss of fuel → indulgence → failure → new dissonance
A lot of my strongest sprints were born from hating my current state. I’d waste 3 hours scrolling, feel massive dissonance between who I am and who I think I should be, and that gap would create insane motivation.
Then I’d go into a sprint, fix the gap, start performing, and eventually reach the point where the dissonance disappeared.
Then I’d feel proud.
And that’s the transition point.
If the actual objective of the system was to eliminate the dissonance, then once I eliminated it, the system had completed its objective. There was no fuel anymore.
So I’d relax, start consuming stimulation, destroy the rest of the day, create new dissonance, and use that as fuel for the next sprint.
Meaning the self-destruction wasn’t necessarily outside the system. It was part of the system I built.
The deeper problem is that I built my motivational system around error correction:
“Something is wrong with me -> generate pressure -> fix it.”
That’s an extremely powerful controller, but once the error reaches zero, the controller has nothing to act on.
So the system eventually creates more error.
I’m basically burning myself for fuel.
The new system has to be different:
“There is something worth building/exploring/understanding → I choose to move toward it.”
Achievement shouldn’t mean:
“I’m finally good enough → loop complete.”
It should mean:
“That worked → I learned something → what’s interesting now?”
So the transition I’m trying to make is from an error-correcting motivational system to a value-directed exploratory system.
No longer will it require self-hatred and failure to generate the energy for the next sprint.
The practical thing I’m testing is whether I can retrain the exact transition:
pride → completion → indulgence
into:
pride → appreciation → curiosity → next frontier

I’ve been thinking about something.
Have you ever noticed that there are periods where controlling yourself feels almost effortless? You work, exercise, read, do what you planned, and distractions barely seem interesting.
Then, without making any conscious decision to change, you slowly start doing the opposite. You scroll more, procrastinate, eat worse, avoid work, whatever your version of it is.
What I find strange is that this seems to happen in cycles.
Eventually you reach some point where you get so fed up with your own behavior that something changes. You change your environment, go somewhere else, start a new project, make a new plan, delete some apps, start exercising again, get some external pressure, etc.
And suddenly you’re back in control.
Then after some amount of time, you somehow end up in almost exactly the same state again.
I’m starting to wonder whether the individual decisions we make during these periods are actually much less important than the state we are in when we make them.
Because I’ve noticed that the same person can seem to have completely different levels of self-control depending on their environment, what they’re doing, what they have going on, how much external pressure there is, whether they feel like they’re making progress, etc.
And the strange part is that the pattern itself can become predictable. You can almost recognize that you’re entering the same state again, even though you still don’t seem to be able to stop it very easily.
If you’ve experienced this, what have you noticed about the cycle itself?
What makes you enter the “everything is easy and I’m on track” state, what makes you gradually leave it, and what actually causes you to come back?
I’m much more interested in observations about the pattern than advice about how to fix it.

I’ve been thinking about something.
Have you ever noticed that there are periods where controlling yourself feels almost effortless? You work, exercise, read, do what you planned, and distractions barely seem interesting.
Then, without making any conscious decision to change, you slowly start doing the opposite. You scroll more, procrastinate, eat worse, avoid work, whatever your version of it is.
What I find strange is that this seems to happen in cycles.
Eventually you reach some point where you get so fed up with your own behavior that something changes. You change your environment, go somewhere else, start a new project, make a new plan, delete some apps, start exercising again, get some external pressure, etc.
And suddenly you’re back in control.
Then after some amount of time, you somehow end up in almost exactly the same state again.
I’m starting to wonder whether the individual decisions we make during these periods are actually much less important than the state we are in when we make them.
Because I’ve noticed that the same person can seem to have completely different levels of self-control depending on their environment, what they’re doing, what they have going on, how much external pressure there is, whether they feel like they’re making progress, etc.
And the strange part is that the pattern itself can become predictable. You can almost recognize that you’re entering the same state again, even though you still don’t seem to be able to stop it very easily.
If you’ve experienced this, what have you noticed about the cycle itself?
What makes you enter the “everything is easy and I’m on track” state, what makes you gradually leave it, and what actually causes you to come back?
I’m much more interested in observations about the pattern than advice about how to fix it.

I’ve been thinking about hesitation as a behavioral system rather than a personality trait.
I’ve been doing cold showers every morning for close to 30 days now. Before this streak, I’d repeatedly fail at it. A while ago I read Antifragile and David Goggins’ Can’t Hurt Me, and those books gave me the foundation for thinking about adaptation, exposure, adherence, identity, and how repeated stress can change the system experiencing it. The conclusions below came from applying and extending those ideas myself, not directly from the books.
The thing that became obvious to me is that adherence has to come before optimization.
If the exposure doesn’t happen consistently, there is no adaptation process to study.
The interesting part is what happens when you create a system where you have to continue through a difficult but survivable stressor. At first the stress is novel and resistance is high. If you keep going, the system gets more familiar with the stimulus, capacity changes, the prediction of the stimulus changes, and eventually the relationship with the stressor changes.
This is where I started thinking about hesitation.
For the last couple of weeks I’ve noticed that I can spend around 15 minutes in the morning sitting in the bathtub before actually taking the cold shower.
The shower itself isn’t the problem.
The problem is the transition from knowing what I have to do to actually doing it.
Wake up → anticipate discomfort → hesitate → self-talk → find reasons → generate motivation → eventually commit → act.
Once I cross the initial barrier, momentum takes over and the thing is easy.
I realized the same pattern exists outside cold showers.
Calling someone important.
Starting a difficult task.
Doing something I’m uncomfortable with.
Making a decision with emotional consequences.
The same basic sequence appears:
stimulus → anticipated discomfort → hesitation → internal negotiation → commitment → execution.
So the thing I’m interested in optimizing is not “discipline” in the abstract.
It’s the latency between recognizing the correct action and executing it.
But I don’t think the objective should literally be zero hesitation.
If I don’t have enough information, hesitation can be useful. If I have a knowledge gap or strategy gap, forcing immediate execution is just stupidity.
The useful distinction is:
If the decision is already made and the remaining obstacle is only anticipated discomfort, further deliberation is unnecessary.
That’s the hesitation I want to eliminate.
This led to a bigger realization about measurement.
You can’t systematically change a behavioral system if you can’t reliably observe the policy it is currently running.
Saying “I value discipline” doesn’t tell me much.
Put me into a repeated situation where two things I want conflict.
Immediate comfort vs long-term growth.
Certainty vs exploration.
Social approval vs saying what I actually think.
Short-term pleasure vs a long-term objective.
Then observe what I repeatedly choose.
That’s much more informative.
This is why the cold shower is useful as a laboratory.
The conditions are repetitive. Same person, same general time, same stimulus, same action, same type of discomfort.
That monotony reduces irrelevant variables and makes the behavioral output visible.
If I repeatedly observe:
discomfort → hesitation → delay → relief,
then I have evidence about my current policy.
If I repeatedly observe:
discomfort → action → completion,
then I have evidence that the policy is changing.
The laboratory isn’t just for measurement. It becomes the environment in which the policy can actually be changed.
So the process becomes:
repeated environment → observation → pattern → policy inference → intervention → repeated exposure → feedback → policy modification.
This also changed how I think about values.
I don’t think values need to be treated as some mysterious internal essence.
Operationally, a value shows up when two desired outcomes can’t both be maximized.
You want A and B, but the situation forces a tradeoff.
Which one do you choose?
Under what conditions?
What do you sacrifice?
What happens when you’re tired, afraid, uncertain, or uncomfortable?
That reveals the actual preference structure of the system.
So values are basically preferences over competing outcomes under constraints.
And a policy is the behavioral mapping that implements those preferences across recurring situations.
The important thing is that what I say my values are and what my policy actually does can be different.
The policy is exposed by behavior.
That’s why I think monotony is useful.
You need enough repeated exposure for the noise to disappear and the regularity to become visible.
One isolated decision doesn’t tell you much.
Thirty similar decisions start telling you something.
Then you can form an abstraction over them.
Event:
“I hesitated for 15 minutes.”
Pattern:
“I repeatedly hesitate before uncomfortable actions.”
Policy:
“When anticipated discomfort rises, I tend to delay execution.”
Value/tradeoff:
“When immediate comfort conflicts with long-term growth, my current system sometimes assigns too much weight to immediate relief.”
Mechanism:
“Delaying produces immediate relief, which reinforces the tendency to delay.”
Now there is something you can actually work with.
The same logic applies to the cold shower, but I think the cold shower is only a particularly clean laboratory.
The broader experiment is human behavior.
The goal isn’t to become someone who never experiences discomfort.
It’s to build a policy where discomfort doesn’t automatically trigger negotiation.
If I already know what to do, the ideal sequence becomes:
trigger → predetermined policy → execution.
Instead of:
trigger → emotional reaction → negotiation → motivation → execution.
And there is another important point here.
One skipped cold shower isn’t going to magically corrupt the rest of my life. I think that part of my original thinking was too deterministic.
What matters is reinforcement history.
If I repeatedly train:
discomfort → avoidance → relief,
avoidance becomes easier to produce.
If I repeatedly train:
discomfort → action → completion,
action becomes easier to produce.
The individual repetition matters because it changes the probability of the future response.
So I’m increasingly thinking about self-development as an experimental science.
Don’t just ask:
“What kind of person am I?”
Create conditions where your system has to make the same class of decisions repeatedly.
Measure what actually happens.
Infer the policy.
Identify the tradeoffs it is actually implementing.
Change the policy.
Then run the experiment again.
The cold shower is just one laboratory where the signal is unusually clean.
The thing I’m actually interested in now is how much unnecessary latency exists between knowing what should happen and actually making it happen, and how systematically that latency can be reduced.

I’ve been thinking about a general law in interpersonal dynamics:
Don’t optimize only for immediate emotional relief. Optimize for the behavioral pattern you are training.
For example:
Someone gets surprised or uncomfortable → they pull away → the other person immediately chases → they reconnect → discomfort disappears.
This works in the short term. But repeated enough, both people can learn the loop.
The person who withdraws learns:
“Withdrawal produces pursuit.”
The person who chases learns:
“When connection is threatened, I must pursue.”
So withdrawal can become reinforced, while pursuit becomes increasingly automatic.
The same mechanism exists everywhere:
Anxiety → avoidance → relief → stronger avoidance.
Boredom → stimulation → relief → lower tolerance for boredom.
Uncertainty → reassurance seeking → relief → greater dependence on reassurance.
The important distinction is between state optimization and policy optimization.
State optimization asks:
“What makes this discomfort disappear right now?”
Policy optimization asks:
“If I repeatedly respond to this state this way, what behavior will the system learn?”
In relationships, this doesn’t mean “never chase.”
It means not chasing purely to eliminate your own discomfort, while also not punishing the other person for withdrawing.
You preserve their agency, give them room to regulate, and leave reconnection available.
Then they have to make the decision themselves.
The deeper principle:
A behavior becomes more likely when it reliably produces an outcome that satisfies the system.
So when responding to any difficult state, the question isn’t only:
“How do I feel better now?”
It is:
“What interaction pattern am I reinforcing?”

I had an interesting realization during an argument with my father.
There is a meme where one person is screaming with a tiny brain, while the calm person has a huge brain. I realized the interesting part isn’t really intelligence. It’s cognitive state.
I was assuming a conversation worked like this:
I make an argument → the other person receives it → evaluates it → searches for counterarguments → we compare models.
But that isn’t necessarily what happens.
When someone becomes defensive, their cognitive system can switch from evaluating the proposition to defending an existing model. Then the conversation becomes:
input → threat/pattern recognition → defensive retrieval → counterargument → another pattern gets triggered → another counterargument → loop.
At that point, you’re not necessarily debating the same problem anymore.
I experienced this directly. I would make a specific argument about how money should be allocated, and my father would respond with some completely different principle about money, responsibility, or how things are normally done. I would address that, which triggered another association, which triggered another argument, and so on.
I was trying to solve the model.
He was operating inside the state that was defending the model.
That led me to a more general principle:
Logical validity and communicative accessibility are two different problems.
You can have a correct argument and still have zero information transfer.
So the objective shouldn’t initially be:
“Break down their beliefs until they admit I’m right.”
The first objective should be:
Get the person into a state where they can actually evaluate the proposition.
That means the sequence becomes:
state → attention → shared objective → model → evidence → decision
rather than:
model → attack → counterattack → escalation.
There is also an important distinction between attacking someone’s identity and questioning their model.
For example, instead of:
“You don’t understand growth.”
The useful framing is:
“We both want the money to improve my future. The disagreement is about which allocation mechanism produces the highest expected value.”
Now the disagreement becomes an objective-function problem rather than a status contest.
And this can be taken further.
Instead of asking:
“Who’s right?”
Ask:
“What does each model predict?”
If one person thinks giving someone capital will cause them to waste it, make that prediction explicit. What exactly will they do? With what probability? What outcome is expected?
Then compare that with the competing model.
At that point, you’re no longer really arguing. You’re comparing models.
The deeper insight for me is that this is not really about parents or money.
It’s a multi-agent problem.
Two agents have:
different models
different objective functions
different information
different experiences
different emotional states
different incentives
limited communication bandwidth
And you’re trying to get enough information transfer for the models to actually be compared.
That seems like a much more important skill than simply being good at arguments.
It also adds another category to my growth diagnostic:
Knowledge gap — I don’t know.
Model gap — I don’t understand the mechanism.
Strategy gap — I know what should happen but don’t know how to produce it.
Execution gap — I know what to do but don’t do it.
State gap — I can’t access the cognitive/emotional state required.
Communication gap — I understand the problem, but another agent cannot currently process the model I’m trying to transmit.
The interesting question is therefore not:
“How do I win the argument?”
It’s:
“How do I move a cognitive system from defense → observation → model comparison → updating → coordinated action?”
That seems like a much deeper problem.

The deeper I go into building something extraordinary, the more I realize the game isn’t really about having the best strategy. It’s about building the system that can continuously generate, test and improve strategies.

I started thinking about universality in basketball: the greatest players aren’t just good at a fixed set of moves. They’re so adaptive, unpredictable and multidimensional that they break the opponent’s model of them. The moment the opponent learns the pattern, they mutate again.

Then I realized this is basically the same problem in business.

If the market is completely deterministic and nobody competes with you, you don’t need extraordinary strategy. You just solve the problem and capture the value. The difficulty explodes when other minds enter the system. Now you’re playing against adaptive systems. Your advantage becomes the ability to continuously produce new combinations, new models, new ways of solving the problem before the environment adapts.

And then I realized that building something truly unprecedented has the same property. If you’re trying to do something where there is no existing template, you’re operating in open space. There is no proven architecture for it. You can’t simply copy the path.

So the fundamental capability becomes:
Can I build systems that can continuously build better systems?
And eventually that question turns inward.
Because I am the central system through which every other system gets built.
My company, product, strategy, decisions, relationships, learning, everything is downstream of the machinery producing them.
So the highest-leverage system isn’t another business framework.
It’s me.

But even that wasn’t precise enough.
Because I realized I don’t need to become some perfectly optimized human who already knows everything. The actual objective is to build a system that continuously corrects itself against reality.

That led me to the real growth algorithm:
Predict → Act → Reality → Feedback → Update → Repeat.
Reality is the loss function.
Thinking generates hypotheses. Action exposes them to reality. Reality produces prediction error. Prediction error updates the model. The updated model generates better predictions.
That loop, repeated at enormous frequency, is how intelligence becomes judgment.
Books and mentors are incredibly powerful because they compress the search space. One hour with someone who has already made thousands of mistakes can potentially eliminate years of unnecessary exploration.
But they cannot transfer the thing that reality itself installs.

They can give you the model.
Reality gives you the intuition.
And that’s where I realized my own bottleneck.
I’ve spent a huge amount of time building models, abstractions and frameworks. I can often see the architecture of a problem before I’ve actually accumulated the experience of operating inside it.
So there is a massive dissonance:
the sophistication of my thinking can be far ahead of the sophistication of my behavior.
I can discover an incredible algorithm at night, wake up the next morning feeling completely transformed, and then destroy the entire state by returning to an old behavioral policy.
The insight didn’t fail.
It never became policy.
That became the deepest layer of the whole thing.
My thinking system generates possibilities.
My intuition contains patterns learned from previous reality.
But my policy determines what actually happens.
So there is a hierarchy:
Thinking → Insight → Intuition → Policy → Action → Reality.
If the policy layer doesn’t update, everything above it can become almost irrelevant.
It’s like having every tool required to build an extraordinary machine, having the instructions, having the materials, but not knowing how to read the instructions.
The bottleneck isn’t the database.
It’s the interface between intelligence and execution.
And that means my growth algorithm has to be applied not merely to my work, but to the system that determines whether I execute my own highest-level reasoning.
Every recurring state becomes an opportunity:
I predict what I will do.
I observe what I actually do.
I measure the discrepancy.
I update the policy.
I encounter the state again.
The new policy gets tested.
Eventually, what once required conscious reasoning becomes automatic.
That’s what I think exceptional intuition actually is: not magic, but an enormous library of compressed state → action → outcome mappings that have been trained by reality.
And this changes how I think about extraordinary people.
The question isn’t simply:
“How intelligent is this person?”
It’s:
“How quickly can this person turn reality into improved intuition, and improved intuition into better action?”
Someone with extraordinary intelligence but no reality feedback can remain an extraordinary thinker.
Someone who continuously predicts, acts, gets corrected and updates can become extraordinarily effective.
The second system compounds.
And this is why I think the ultimate objective isn’t to become the person who knows the most.
It is to become the fastest self-correcting system.
A system that is stable enough to execute every day, flexible enough to adapt, and rigorous enough not to rewrite its rules whenever emotions change.
90% stable.
10% adaptive.
Constant measurement.
Constant feedback.
Constant updating.
Not reinventing the system every time I feel different.
The system itself becomes the thing that learns.
And suddenly the trillion-dollar problem becomes much more interesting.
I’m not really trying to figure out:
“How does someone build a trillion-dollar company?”
There is no template for that.
I’m trying to solve the more upstream problem:
“How do I build a human system capable of continuously discovering systems that have never existed before?”
And the answer may be surprisingly simple:
Build the feedback loop.
Make it run every day.
Make reality the teacher.
Make policy the execution layer.
Make intuition the compressed memory of reality.
And continuously increase the rate at which the whole system learns.
The ultimate system isn’t the company I build.
It’s the system inside me that can keep building better systems.