乘物游心录 · Technical Notes

Understanding is not storing information

Mon, 20 Jul 2026 09:00:00 +0800

After reading a passage, it is easy to mistake recall for understanding. Repeating the author’s conclusion is useful, but it mainly demonstrates successful storage and retrieval. The words may be available while the argument remains foreign.

Return from the conclusion to the problem
#

One test of understanding is to set the conclusion aside and ask what problem the explanation was designed to solve. Its value lies not only in what it asserts, but also in the tempting alternatives it rules out.

From a Beam of Light to an Alloy Layer: The Laser Cladding Process Window

Fri, 17 Jul 2026 21:30:00 +0800

Laser cladding is not as simple as “burning powder onto a part.” It is an energy–material–motion coupling that unfolds at millimeter and millisecond scales: the beam determines heat input, powder determines composition and mass, the melt pool determines the final structure, and the toolpath determines whether a local process can be repeated across an entire part.

Surface hardening Remanufacture and repair Directed energy deposition Digital process engineering

From 'It Runs' to 'It Can Be Maintained': Three Foundations of Reliable Systems

Wed, 15 Jul 2026 09:30:00 +0800

A system being able to start only proves that it passed the earliest gate. Once it reaches production, teams care about three questions: Can we locate a problem quickly? Will a local fault spread? Can every release be controlled?

Reliability is not a one-time acceptance check before launch. It is an engineering capability that keeps shortening the time from discovery to containment to recovery. These three foundations connect in order: make the system explain what happened, keep a fault inside its boundary, and give every change a safe way out.

Why efficiency can create more waste

Sun, 12 Jul 2026 09:00:00 +0800

Efficiency is usually treated as an unquestioned good: machines should not sit idle, people should not wait, and every minute should be used. In an interdependent system, however, keeping every local resource busy often moves waste instead of removing it.

Activity is not throughput
#

When one step finishes work that the next step cannot accept, the apparent output becomes inventory, queues, and coordination overhead. The utilization report improves while the result customers need arrives no sooner.

Connect an AI Assistant to the Development Workflow: Optimize the Feedback Loop First

Fri, 10 Jul 2026 14:00:00 +0800

When people discuss AI-assisted programming, attention often goes to how much code a model can write in one pass. In a real project, a more useful measure is how long it takes to move from a proposed change to trustworthy verification.

Split work into verifiable units
#

A good task usually satisfies three conditions at the same time:

Technical Writing Is Not Filing Information; It Is Building Searchable Judgment

Fri, 03 Jul 2026 20:10:00 +0800

Saving links preserves information, but rarely preserves judgment. A few months later, what matters is often not what was read, but why a solution was chosen and under which conditions it remains valid.

Four kinds of information an article should keep
#

Context
#

Explain which system, scale, and constraints the problem came from. Without context, an experience is easily reused in the wrong setting.

The history of technology is first a history of organization

Sun, 28 Jun 2026 09:00:00 +0800

Technology history is often told as a sequence of inventions: a laboratory makes a breakthrough, a company launches a product, and a performance curve rises. Technologies that reshape society rarely travel on an invention alone. They must pass through manufacturing, standards, capital, skills, and supply chains before they become dependable infrastructure.

Leave a place for uncertainty

Tue, 19 May 2026 09:00:00 +0800

Project plans often express commitment through a single date, budget, and outcome. The danger is not commitment itself. It is the implication that sufficient detail can make uncertainty disappear. Deviations then look like execution failures, bad news gets hidden, and the plan loses its value as a decision tool.

Good design works before the error

Fri, 03 Apr 2026 09:00:00 +0800

Many systems treat error handling as a clearer message shown after failure. That is better than silence, but it still arrives after the mistake. Better design moves forward in time and helps people understand their options and consequences before acting.

Make possible actions visible
#

When an interface shows outcomes but hides state, users must guess at the next step. Visibility means showing where they are, what can be done, which actions are unavailable, and what will happen after completion.

Break large problems into repeatable small ones

Mon, 16 Mar 2026 09:00:00 +0800

“Break the big problem into smaller ones” is common advice. But a longer task list does not automatically reduce complexity. Dependencies can remain tangled, information can disappear at hand-offs, and every small task may still be a one-off that must be reinvented next time.

About 乘物游心录

Mon, 01 Jan 0001 00:00:00 +0000

Technical Notes is a long-term knowledge archive for people who build and operate real systems. It focuses not only on what works, but on why it works, how to verify it, and where it stops working.

Why write
#

Useful technical knowledge keeps its context: the problem, constraints, alternatives, evidence, and remaining uncertainty. New practice should refine old conclusions, and new evidence should be allowed to change them.

Interactive Laser Welding Learning Lab

Mon, 01 Jan 0001 00:00:00 +0000

Topics

Mon, 01 Jan 0001 00:00:00 +0000

Topics group related articles into a continuous path, from underlying mechanisms to practical engineering decisions.

乘物游心录 · Technical Notes

Understanding is not storing information

Return from the conclusion to the problem #

From a Beam of Light to an Alloy Layer: The Laser Cladding Process Window

From 'It Runs' to 'It Can Be Maintained': Three Foundations of Reliable Systems

Why efficiency can create more waste

Activity is not throughput #

Connect an AI Assistant to the Development Workflow: Optimize the Feedback Loop First

Split work into verifiable units #

Technical Writing Is Not Filing Information; It Is Building Searchable Judgment

Four kinds of information an article should keep #

Context #

The history of technology is first a history of organization

Leave a place for uncertainty

Good design works before the error

Make possible actions visible #

Break large problems into repeatable small ones

About 乘物游心录

Why write #

Archive

Interactive Laser Welding Learning Lab

Topics

Return from the conclusion to the problem
#

Activity is not throughput
#

Split work into verifiable units
#

Four kinds of information an article should keep
#

Context
#

Make possible actions visible
#

Why write
#