FULL-TEXT REPRINT · COLLECTED READING

韩先凯 著(笔名:离谱) · byoungd and contributors

Original chapter · GitHub · CC BY-NC 4.0 · 中文原作

Noncommercial reprint. Prose is retained; layout and internal links are adapted. Collected on 2026-10-13 · Source updated 2026-10-02 · f13ff2de

On this page

Improving Yourself: Make Growth a Verifiable Long-Term Experiment

“Improve yourself” is a sentence capable of carrying almost any anxiety. Learn English, become healthier, change jobs, build a product, become more stable: all can be called improvement. Because it can point anywhere, it often has no executable shape.

If improvement means continually disliking who you are now, it becomes a treadmill with no finish. Goals rise, standards rise, and the speed at which you judge yourself rises, but no moment is allowed to confirm that an ability has actually become yours.

A more reliable improvement process resembles a small experiment. Name the situation it serves, keep a baseline, choose one action, accept real feedback, and decide after a defined cycle whether to continue, transfer, repair, or stop. An experiment cannot guarantee success, but it lets evidence adjust your life instead of imagination alone.

What This Chapter Covers

  • Turn vague wishes into concrete situations and completion standards;
  • Distinguish input, practice, artifacts, and transfer evidence;
  • Let feedback change an action without letting one comment define a person;
  • Use AI to speed iteration while keeping human judgment;
  • Use a 90-day cycle and clear exit doors for improvement.

1. Ask What the Improvement Is For

“I want to improve my English” is a direction, not a goal. Add four elements:

The real situation where I will use it:
The exact point where I am stuck in that situation:
The observable result someone will see when it works:
The upper limit of time, money, and attention I will invest:

For example, turn “improve speaking” into “In the weekly client meeting, explain progress, risks, and next steps in English; when questioned, confirm the question before answering.” Once a goal enters a situation, practice knows what to simulate and feedback knows what to name.

If an improvement has no user, situation, or cost, it may be an image of a future self. Imagination is not bad, but it cannot manage time by itself.

2. Let a Baseline Protect You from Exaggeration and Denial

Before starting, keep an unpolished sample: a recording, an email, a real task, a workflow, or one week of life. A baseline does three things:

  • It stops unfamiliarity from being mistaken for complete inability;
  • It stops short-term excitement from being mistaken for stable ability;
  • It lets you compare at the end of a cycle instead of relying on the mood of memory.

An English baseline might include a 60-second monologue on a familiar topic, three questions on an unfamiliar topic, a listening summary, and a real work email. Do not correct it first. Mark facts: pauses, misunderstandings, omissions, and whether the other person had to ask again.

A baseline is not a public score. It belongs to the experiment, not to your personality.

3. Separate Input, Practice, Artifacts, and Transfer

Many claims that “effort had no effect” come from mixing four different activities:

TypeWhat it solvesTypical evidence
InputRecognise concepts and examplesExplain the point in your own words
PracticeImprove an action under controlled conditionsFewer errors or greater speed on similar tasks
ArtifactComplete a deliverable within constraintsSomeone has seen, used, or commented on it
TransferComplete a task under a new conditionIt still works with a new topic, listener, tool, or pressure

Ten hours of lessons mainly increase input; they do not prove that you can explain a risk in a meeting. Repeated recordings can improve practice; real conversation still has to test transfer. Schedule at least one artifact and one transfer task per cycle, or improvement will remain in a familiar room.

4. Change One Major Variable at a Time

Changing the materials, teacher, tool, time, and goal together removes your ability to tell what caused a change. A comparable cycle changes one major variable, for example:

  • Keep the topic and shorten preparation time;
  • Keep the task and change the real listener;
  • Keep the material and change AI from immediate rewriting to after-the-fact feedback;
  • Keep the workflow and turn off one source of notifications.

Life will not be a clean laboratory. Record unavoidable changes instead of pretending they did not happen. The point is to leave judgment a little space.

5. Let Feedback Change an Action, Not Define a Person

The most useful feedback is not “you are not good enough.” It is “under these conditions, this action produced this result.” After receiving feedback, take three steps:

  1. Locate: Does it concern a fact, a task, or an impression in a relationship?
  2. Verify: Can a second sample show that the problem repeats?
  3. Change: What one action will change next time, and when will you check again?

If someone says your English explanation “sounds roundabout,” do not jump to “I am bad at expressing myself.” Ask whether the opening lacks a conclusion, the sentences are too long, the sequence is missing, or the listener lacks context. In the next explanation, give the conclusion, two facts, and one request. Feedback has become an action, not an identity.

Some feedback will not fit. It may come from a mismatched setting, a preference difference, or insufficient information. Respecting feedback does not mean obeying all of it. Use more samples to decide whether it belongs in your system.

6. AI Can Speed Iteration, Not Choose Your Direction

AI can simulate different listeners, identify repeated errors, generate contrastive exercises, organise feedback, and break a task into smaller steps. It should not replace your definition of the problem, responsibility for risk, or confirmation of the real result.

Before using AI, write three lines:

My judgment or first draft:
The specific issue I want AI to check:
The evidence I will use to decide whether to accept it:

Write an English risk explanation yourself first. Then ask AI to flag ambiguous sentences and offer two tones. You choose the final version in light of the real relationship, responsibility, and facts. If AI generates from a blank page, the prose may be smooth while your understanding and accountability disappear.

Archive each AI use as input, output, human revision, and real-world feedback. Without the last two, it is tool experience, not capability growth.

7. Use Ninety Days for a Deliverable Improvement

A 90-day cycle can have five stages:

StageCore questionMinimum result
Weeks 1–2What are the baseline and real bottleneck?One baseline sample and one main question
Weeks 3–6Which action deserves repetition?6–10 comparable practices
Weeks 7–10Can it become a real artifact?One delivery and at least two pieces of feedback
Weeks 11–12Can it transfer, and is the cost sustainable?One new-setting test and a closing record
Days 85–90What will I retain, hand off, or change next cycle?One final sample and a decision for the next cycle

Keep one main question each week, such as “Confirm before answering under questioning,” instead of chasing vocabulary, pronunciation, speed, humour, and confidence at once. At the end, choose continue, transfer, repair, or stop. Stopping a direction with insufficient evidence or excessive cost is an experimental result, not a personality failure.

8. Set Exit Criteria for Long-Term Goals

Give every long-term goal at least four clear exit criteria:

  • Value criterion: Does the real situation and user still exist?
  • Evidence criterion: What result supports continuing, and how long without it triggers review?
  • Cost criterion: What are the red lines for sleep, income, relationships, and safety?
  • Responsibility criterion: What handoff, explanation, or repair is required if you stop?

Clear exit criteria let you invest seriously because the investment is not bottomless. They keep sunk cost from becoming a reason to consume more.

9. A Thirty-Day Improvement Experiment

If 90 days feels too heavy, test one hypothesis for 30 days:

My hypothesis: If I repeat ___ action under ___ conditions, ___ result will improve.
Baseline sample:
Repetitions per week:
Feedback I will keep:
Signals that make continuation not worthwhile:
Day-30 decision: continue / transfer / repair / stop

Do not add goals mid-cycle. Make one short review each week: Which condition made the action easier? Which made the result worse? Should the task be smaller instead of the requirement higher?

Conclusion: Let Progress Leave the Imagination

Improving yourself does not mean driving the present person away and replacing them with someone more deserving of affection. It means making a real person more reliable in a real situation: able to hear the problem, judge, deliver, accept revision, and change direction when evidence says so.

You will meet stagnation, regressions, mistakes, and unsuitable goals. They do not need to be packaged as inspiring stories or written as permanent verdicts. Put them into cycles, samples, feedback, and boundaries, and let reality answer again.

When your ability still works with a new listener, a new task, and an imperfect day, improvement has left the imagination and entered life.