Early experience can choose what you see next¶
Cross-Domain EchoesShared pattern · Path Dependence
An early success or failure can change which option someone tries again and how they interpret later results. That is the path-dependent learning pattern called outcome primacy. A software team’s fluency with one tool can similarly skew later tool choices: the visible effort of learning an alternative looms larger than the deferred cost of forcing the familiar tool onto a poor fit. Both show history influencing not only a present preference but the process that could correct it. The first is about learned value and subsequent sampling; the second is about asymmetric cost salience in tool selection. Familiarity is not always a mistake. The software anti-pattern requires that the misfit does more harm than the saved acquisition cost justifies.
Choose a role to see its counterpart in both examples. The diagrams show relationships, not measured quantities.
Decision psychology
Early outcomes reshape later sampling
Read Outcome primacyDomain-specific abstraction
Initial reinforcement changes value and sampling, helping its influence persist when later evidence is missed or discounted.
In this example: A durable first-outcome effect must be distinguished from ordinary sampling variation or recent evidence.
Software architecture
Fluency can distort the next tool comparison
Read Golden Hammer Anti-PatternDomain-specific abstraction
Past mastery makes alternative acquisition salient while the familiar tool’s misfit costs remain deferred or attributed elsewhere.
In this example: Reuse becomes an anti-pattern only where misfit harm exceeds the defensible savings from familiarity.
History supplies more than background: it shapes the later comparison.
Written comparison
The historical starting point
Decision psychology
The first experienced task outcome
Software architecture
A team’s already-mastered capability
History supplies more than background: it shapes the later comparison.
The comparison is tilted
Decision psychology
Anchored value or rare-event weighting
Software architecture
Salient acquisition cost versus deferred misfit
The tilting mechanisms differ; neither is reduced to a generic dislike of change.
Choice affects what can correct it
Decision psychology
Sampling changes later exposure
Software architecture
Tool choice puts misfit into delayed outcomes
The return arrows represent a possible self-maintaining skew, not a fixed psychological law or inevitable lock-in.
What carries across
When a historical preference persists, examine how it steers later exposure and comparison. The apparent absence of contrary evidence may partly be an effect of the preference itself.
Where the comparison stops
Outcome primacy is a learned-choice phenomenon; a software team’s staffing, training and tool costs are real organizational constraints. The same intervention need not correct both.
- The golden hammer is not every familiar-tool choice and not simply the sunk-cost fallacy. A credible better-fitting alternative and net misfit harm must exist.
- The diagrams do not imply permanent lock-in or that every initial experience dominates later evidence.
Conditions for this comparison
- The first-outcome effect persists with task and later evidence made comparable.
- The software case distinguishes justified reuse from a harmful mismatch, including the actual costs of alternatives.
Source entries
Shared pattern
Path Dependence
Prime
Core Idea
Outcomes are determined not only by current conditions but by the specific historical trajectory of choices, where past decisions constrain present options and lock in consequences that persist despite present incentives to change, as Arthur (1989) formalized in his model of competing technologies under increasing returns.
Decision psychology
Outcome primacy
Domain-specific abstraction
Core Idea
Outcome primacy describes path-dependent behavior after early success or failure, particularly when the first outcome anchors a representation of rare-event likelihood before enough experience accumulates.
Software architecture
Golden Hammer Anti-Pattern
Domain-specific abstraction
Core Idea
The structural mechanism is asymmetric cost salience in tool-selection decisions.
What It Is Not
The anti-pattern names only the point where that bias has crossed into *net harm*, where the misfit cost exceeds the saved acquisition cost. Defensible switching-cost reuse and pathological inertia are different sides of a parameter-located line.