Build the mental model

Overfitting is the gap between remembering the examples used to fit a model and learning a pattern that works on unseen examples. Training accuracy can improve while validation accuracy stalls or falls; that divergence, not simply a high score, is the warning.

A reliable beginner model has three boxes: input, transformation, and evidence. The input is what enters the system; the transformation is what the technique actually computes or changes; the evidence is how we learn whether the output works beyond one attractive example. For this topic, the transformation is not magic: A flexible model has enough parameters or decision boundaries to absorb both signal and accidental noise. During fitting, optimization minimizes training loss, so it is rewarded even for memorizing quirks. A held-out validation set estimates generalization because its labels did not influence those updates. Regularization, simpler hypotheses, early stopping, and more representative data constrain memorization.

The boundary matters. Do not confuse a mechanism with an outcome. A mechanism can make a desired outcome more likely while still failing on a particular case. It also does not erase the need for source checks, permissions, or domain judgment. The practical question is therefore not “Does it work?” but “Under which inputs, constraints, and measurements does it work well enough?”

A spam classifier has 99% training accuracy and 84% validation accuracy. Reducing tree depth moves those to 93% and 91%. The second model is preferable because its estimated generalization gap shrinks from 15 to 2 percentage points.

The worked number is generalization gap = training score − validation score = 0.99 − 0.84 = 0.15. State the unit and denominator whenever you report it. A percentage without a denominator can conceal a tiny sample; a latency without a percentile can conceal slow users; a similarity score without a labeled task can conceal irrelevant neighbors. Compare the observed value with a threshold chosen before seeing the final test result.

Now test the tempting shortcut. Suppose the team optimizes only the most visible metric. The result may look better while the system becomes less trustworthy. The reason is concrete: Too little capacity underfits real structure; too much fits noise. Strong regularization lowers variance but can add bias. More training data usually helps, but only if it represents deployment conditions. Repeatedly tuning on the test set quietly turns that test set into training data. This is why the decision record must include both the intended gain and the tolerated regression. If the tolerated regression is unknown, the change is not ready for a consequential workflow.

• Prefer a measured baseline over a persuasive demo.
• Keep versions, inputs, and thresholds reproducible.
• Separate syntactic success from semantic correctness and authorization.
• Escalate or abstain when evidence falls outside the contract.
• Re-evaluate when data, traffic, models, providers, or user goals change.

These rules turn the topic into an engineering decision rather than a slogan. They also make disagreement productive: another person can challenge the assumptions, rerun the evaluation, and reach a documented conclusion.

Create one near-example and one counterexample. The near-example should differ from the scenario in only one important way; the counterexample should look similar while requiring a different technique. For each, label the input, the transformation that actually occurs, and the evidence you would accept. This exercise prevents the topic name from becoming an all-purpose explanation. If you cannot say what would falsify your mental model, it is still a story rather than a model. End with one sentence beginning “This technique does not guarantee…” and make that limitation observable.