MENTAL MODEL · M1591

Boat Anchor

BusinessHigh supportManagement

Included

Version 1.0.0 · Updated 2026-07-30

CORE DEFINITION

Refers to a piece of code or functionality retained in a codebase that is no longer useful (not called), but is kept because developers fear "it might be useful later" or "we don't know what will happen if we delete it," dragging down the system like an anchor.

SCAFFOLDING EFFECT

psychology

Reduce cognitive load

Decisively cut off and let go. In life and management, regularly clean up those "boat anchors" (outdated regulations, old businesses no longer maintained, dusty clutter). If it might be useful later, version control (History) can retrieve it; delete it now.

anchor

Anchor fast decisions

The software anti-pattern "Boat Anchor": retaining code/functionality/assets that are no longer called or valuable, often with the rationale "might be useful" or "afraid of breaking something if deleted." The cost is continuously slowing down the system (cognitive load, maintenance cost, risk of misuse), while version control already guarantees recoverability. Essentially, it is irrational retention caused by "sunk cost + loss aversion."

MINIMUM ACTION

In progress 0/1

Practice this model in one real situation:

Conduct regular audits: list "boat anchors" that are not called or create no value. 2. Confirm that version control/backups can restore, eliminating the fear of "can't retrieve after deletion." 3. Set deletion criteria (e.g., remove if unused for N cycles). 4. Delete and verify no regression. 5. Similarly, clean up outdated regulations, old businesses, and backlogged clutter at the organizational level.

Check to track your progress (stored locally)

Learning progress0%

account_treeGenealogyexpand_more

menu_bookReferencesexpand_more

Source support: Explicit

link
zh.wikipedia.orghttps://zh.wikipedia.org/wiki/%E9%94%9AZH · Explicit
verified

RELATED MODELS