https://www.raygorous.comLife, The Universe, and Everything2026-04-27T08:32:44.479Zhttps://github.com/jpmonette/feedraygorousray@raygorous.comhttps://www.raygorous.comIf you can judge it, you can learn it.https://www.raygorous.com/favicon.icoAll rights reserved 2026, raygorous<![CDATA[把自己从自动驾驶里叫醒 (4min read)]]>https://www.raygorous.com/article/wake-yourself-up-from-autopilot2026-04-23T08:03:42.763Z
]]>2026-04-21T00:00:00.000Z<![CDATA[Visualization Is Not About Winning. It Is About Rehearsal.]]>https://www.raygorous.com/article/visualization-is-not-about-winning-its-about-rehearsal2026-04-20T05:00:50.198Z
For a long time, I misunderstood visualization.
I thought it meant closing my eyes and generating a cinematic picture of success: the launch going well, the deal closing, the audience applauding, the future self already living in the outcome.
That version always felt emotionally pleasant. It also rarely made me more effective.
The more I read, the more I think the useful form of visualization is something else entirely.
It is not fantasy.
It is rehearsal.
That distinction matters because the two forms do almost opposite things.
1. Outcome fantasy gives you emotional reward before the work
When we visualize the finished outcome, we often simulate arrival instead of effort.
We picture the achievement, not the sequence that earns it.
We imagine having the thing, not doing the thing.
That can feel motivating in the moment, but it can also create a subtle trap: the mind consumes part of the reward in advance.
Research associated with Gabriele Oettingen's work on positive fantasies points in this direction. If you spend too much time mentally enjoying the desired future, you may mobilize less energy to pursue it. The fantasy becomes a kind of emotional substitute for action.
That explains a lot.
Some forms of visualization do not fail because they are "not positive enough." They fail because they are too satisfying too early.
If the exercise leaves you soothed but less ready to act, it was probably not preparation. It was sedation.
2. Process rehearsal gives your brain extra reps
The stronger version of visualization is much more concrete.
Instead of imagining the trophy, you imagine the sequence.
Instead of imagining the applause, you imagine the first move.
Instead of imagining the perfect ending, you imagine the difficult middle.
This is where the neuroscience becomes interesting.
Studies on motor imagery and mental practice suggest that vividly imagined action can recruit some of the same planning and motor systems involved in real performance. That does not mean imagination is equivalent to reality. It means vivid simulation can function like training data.
In other words:
That helps explain why mental practice shows up so often in high-performance domains. Athletes use it. Surgeons use it. People preparing for difficult conversations use it. The mechanism is different from "manifestation." It is closer to pre-exposure.
You are making the task less novel before it arrives.
3. Elite performers do not visualize trophies. They visualize sequences.
One of the most useful patterns in performance psychology is this:
Top performers rarely spend their mental energy on the ending.
They spend it on the execution.
The best stories from sport and surgery all have the same structure.
The performer has already rehearsed:
the opening move
the transitions
the likely mistakes
the recovery after something goes wrong
That is why the Michael Phelps story is so memorable. The point is not just that he visualized winning. The point is that he reportedly rehearsed the entire race so thoroughly, including failure modes, that when something actually went wrong, the moment still felt familiar enough to execute.
The same logic appears in surgical training and military rehearsal. The goal is not optimism. The goal is reducing surprise.
You want the real event to feel like confirmation of a sequence you already know, not discovery of a situation you have never inhabited.
That is a very different use of the imagination.
4. The obstacle is not a flaw in the visualization. It is the point.
A lot of people use visualization to avoid discomfort.
But the useful version does the reverse.
It forces you to meet difficulty early.
That is why WOOP is such a useful framework:
Wish
Outcome
Obstacle
Plan
The obstacle is the hinge.
Without it, visualization becomes entertainment.
With it, visualization becomes preparation.
If I am rehearsing a hard task, I do not want to imagine everything going perfectly. I want to imagine the moment I lose momentum, the moment I hesitate, the moment I get frustrated, the moment the other person responds in the worst plausible way.
Then I want to rehearse my response.
This is especially powerful for anxiety.
Anxiety often feeds on vagueness. The mind runs chaotic simulations with no structure and no exit. Deliberate rehearsal is different. It gives the mind a sequence, a fallback, and a path through the uncertainty.
You are not promising yourself that things will go well.
You are proving to yourself that if they do not, you still know what to do next.
5. A practical template I actually trust
This is roughly how I think about visualization now.
1. Pick one real task happening soon
Not "my future success."
Something specific:
tomorrow's writing session
a difficult conversation
a presentation
a negotiation
a workout
Specificity matters because the brain rehearses sequences better than abstractions.
2. Run the sequence, not the outcome
Start from the first move.
Where are you?
What are you doing first?
What happens next?
What is the part where you usually lose focus?
3. Include friction on purpose
Imagine the interruption.
Imagine the doubt.
Imagine the mistake.
Imagine the moment where the plan feels harder than expected.
Then rehearse recovery.
4. Make it vivid but brief
This does not need to be a long meditation.
A few focused minutes is often enough.
The point is not spiritual depth. The point is useful mental reps.
5. Move into action immediately afterward
The shortest gap between rehearsal and execution is usually the best one.
Visualization should lead into work, not replace it.
6. Pair it with physical reps
This is important.
Mental practice is not a substitute for doing the thing.
It is a force multiplier for doing the thing.
The most credible research in this area points in the same direction: mental rehearsal helps, physical practice still matters more, and the combination is often strongest.
]]>2026-04-19T00:00:00.000Z<![CDATA[You Don't Need Certainty. You Need a Decision System]]>https://www.raygorous.com/article/you-dont-need-certainty-you-need-a-decision-system2026-04-20T00:24:30.064Z
For a long time, I treated hard decisions like hidden-answer exams.
If I thought long enough, compared enough, and read enough, eventually the right answer would reveal itself.
I no longer think that is true.
Most important decisions are not puzzles. They are bets.
Whether you are choosing a role, a city, a project, a relationship, or the next few years of your life, the future is only partly visible. You are making a move under uncertainty. That means the goal is not to eliminate uncertainty. The goal is to build a system that helps you make better bets.
This is the framework I keep coming back to.
1. Stop asking, "What is the right answer?"
That question sounds wise, but it often creates the wrong behavior.
It makes us wait for certainty.
It makes us confuse anxiety with rigor.
It makes us believe that if we are still unsure, we must not have thought hard enough.
But many high-stakes decisions do not come with proof.
A better question is:
What are the key uncertainties here, and how can I reduce them without freezing?
That shift matters. It turns decision-making from a search for certainty into a process of structured learning.
2. Expand the option space before you optimize it
One of the most common decision mistakes is surprisingly simple:
we compare too few options.
Most people think they are making a careful choice, but in reality they are just choosing between the two options that happened to be visible first.
That is dangerous because analysis cannot rescue a bad option set.
So before comparing A vs B, ask:
What options am I not seeing yet?
What would the "third way" look like?
Is there a lower-risk bridge option?
Am I solving the problem I have, or the problem I framed too narrowly?
The quality of a decision often depends more on the quality of the options than on the sophistication of the comparison.
3. Separate ranking from uncertainty
A useful mental model is this:
Most people mash these two together. They say they are "thinking about the decision," but they are actually mixing up:
their current best guess
the parts they still do not know
It is much cleaner to split them.
First, write your rough ranking today.
No perfection. Just the best honest ordering you have right now.
Then write the 2-3 uncertainties most likely to change that ranking.
That forces clarity. It stops you from researching everything and starts pushing you toward the few unknowns that actually matter.
4. Replace overthinking with cheap experiments
A lot of decisions feel impossible because we are trying to answer them inside our heads when they should be answered in reality.
If a cheap test can teach you more than another 10 hours of rumination, run the test.
The ladder usually looks something like this:
Read foundational material.
Talk to people who have actually done it.
Do a small, bounded project.
Simulate the real thing.
Make the bigger commitment only after the smaller tests teach you something.
This applies much more broadly than career decisions.
Before moving somewhere, spend real time there.
Before starting a company, try selling something.
Before committing to a field, build a project in it.
Before taking a massive leap, design a smaller version of the leap.
Do not spend in anxiety what you could spend in experiments.
Reality usually has much better bandwidth than imagination.
5. Only study the questions that can change the ranking
Some questions are interesting.
Some questions are important.
And a much smaller set are actually decision-relevant.
The right test is simple:
If I learned the answer to this question, would it change my ordering of the options?
If the answer is no, it may still be intellectually interesting, but it is probably not where your decision energy should go.
This is where many smart people get stuck. They research large, abstract questions because those questions feel serious. But seriousness is not the same thing as usefulness.
Useful questions are narrower.
They are sharper.
They move the ranking.
Instead of researching everything, identify the few variables that would actually flip your choice.
That is where learning creates leverage.
6. Value upside, reversibility, and option value
Not every decision should be optimized for immediate comfort.
Some choices are valuable because they have:
limited downside
meaningful upside
strong learning value even if they fail
the ability to keep future options open
That combination matters a lot.
Sometimes the best move is not the one with the highest average comfort. It is the one that creates the best future option set.
A useful lens is reversibility.
Ask:
If I choose this and it does not work, how hard is it to come back?
Does this path close doors, or open them?
Am I choosing a result, or buying an option on a better future?
When the downside is survivable and the upside is nonlinear, the decision should not be judged only by the average case.
Some bets are worth taking because they expand who you can become.
7. Build the adaptation layer into the decision itself
A mature decision is not just:
"I choose A."
It is:
I choose A.
If A starts failing, here is Plan B.
If things go badly, here is the downside I can tolerate.
In 3 or 6 months, here is how I will review the evidence.
That last part is underrated.
Many people feel pressure because they think every major decision must define the next decade.
]]>2026-04-19T00:00:00.000Z<![CDATA[Top 5 Most Surprisings From Claude Code Source Map]]>https://www.raygorous.com/article/top-5-most-surprisings-from-claude-code-source-map2026-03-31T17:13:00.294Z
Let’s take a driver seat to look at some of the most surprising findings from the Claude Code source map leak.
There's a Tamagotchi virtual pet system (buddy/)
A full companion system with 18 species (duck, dragon, axolotl, capybara...), rarity tiers (common 60% → legendary 1%), stats like DEBUGGING, PATIENCE, CHAOS, WISDOM, SNARK, hats (crown, wizard, propeller, tinyduck), and a 1% shiny variant chance. Your companion is deterministically generated from a hash of your account UUID using the Mulberry32 PRNG — so it's always the same across sessions. ASCII sprites are 5 lines × 12 chars with 3 animation frames. The /buddy teaser appeared in rainbow text during April 1–7, 2026 only, deliberately rolling across timezones for "sustained Twitter buzz instead of a single UTC-midnight spike." Species names are hex-encoded (String.fromCharCode(0x63, 0x61, 0x70, ...)) to avoid false-positiving a grep that checks build output for internal model codenames.
A "dream" system runs background memory consolidation (services/autoDream/)
When enough time and sessions have passed, Claude Code spawns a background subagent with a literal dream prompt:
"You are performing a dream — a reflective pass over your memory files. Synthesize what you've learned recently
into durable, well-organized memories." It reads your memory files, gathers signal from daily logs and
transcripts, consolidates into topic files, and prunes stale info. A file lock prevents concurrent dreaming across processes. It surfaces as a task pill in the UI footer.
A pure TypeScript port of Meta's Yoga flexbox engine (native-ts/yoga-layout/)
Rather than shipping a native C++ binary, the team reimplemented Meta's Yoga layout engine (~2500 lines of
CalculateLayout.cpp) in pure TypeScript — flex-direction, flex-grow/shrink/basis, align-items, justify-content,
margin/padding/border/gap, absolute positioning, flex-wrap, baseline alignment, display:contents, the works. The
terminal also has a full DOM hit-testing system for mouse clicks that walks a node tree to find the deepest
element under the cursor, bubbles click events through parentNode, and implements onMouseEnter/onMouseLeave with
correct non-bubbling semantics — matching browser behavior exactly, but in a terminal.
"Undercover mode" for Anthropic employees (utils/undercover.ts)
When Anthropic employees use Claude Code on public/open-source repos, it auto-enters undercover mode — instructing
Claude to write commit messages as a human would, never mentioning internal codenames (e.g., "Capybara",
"Tengu"), unreleased version numbers, internal repo names, Slack channels, or the phrase "Claude Code." There is
no force-off — the only escape is being in a confirmed internal repo.
A 2-stage LLM security classifier guards auto-mode (utils/permissions/yoloClassifier.ts)
When you enable auto-mode (no permission prompts), every tool call runs through a separate Claude API call acting
as a security classifier. Stage 1 is a fast pass (max_tokens=64) with the nudge "Err on the side of blocking.
<block> immediately." Stage 2 only fires if Stage 1 blocks — it uses chain-of-thought reasoning (max_tokens=4096)
to reduce false positives. Prompt caching is used strategically so Stage 2 gets a guaranteed cache hit on Stage
1's prefix. The fail mode is always "block" — unparseable responses are treated as blocked. There's even a branded
TypeScript type called AnalyticsMetadata_I_VERIFIED_THIS_IS_NOT_CODE_OR_FILEPATHS that forces callers to
explicitly attest they checked analytics payloads for privacy violations.
Honorable mentions: a full vim state machine for the input box, a /lorem-ipsum skill using words empirically
verified to be single-token, a /teleport command that bundles the repo for remote agents, and the ultrathink