Framework
metaphor dead folk
Source: Carpentry → Abstract Organization
Categories: linguisticssoftware-engineering
From: Carpentry and Woodworking
Transfers
In building construction, the frame (or framework) is the wooden skeleton that defines the structure: studs, joists, rafters, headers, and sills. It is erected after the foundation and before everything else. The frame determines the building’s shape, its load paths, the location of openings, and the dimensions of every room. Once framed, a building’s fundamental geometry is fixed. Changes to the frame after sheathing and finish are installed are enormously expensive — they require tearing out completed work to access the bones.
“Framework” is among the most thoroughly dead metaphors in English. It appears in philosophy (conceptual frameworks), software engineering (web frameworks), management (strategic frameworks), education (curricular frameworks), and policy (regulatory frameworks). In none of these contexts do speakers think of wooden studs at 16-inch intervals. But the source domain’s structural properties continue to operate beneath the surface:
- Skeleton before substance — framing happens first. The carpenter cannot install drywall without a frame to screw it to. The metaphor transfers this priority: a “framework” in any domain is the structure you establish before filling in content. A strategic framework precedes strategic initiatives. A software framework precedes application logic. The structural claim is that the framework is prior, and that filling in content without a framework produces work that has no load-bearing structure.
- Constraint as enablement — a frame constrains everything built within it: you cannot put a window where there is no header, or a door where there is no rough opening. But these constraints enable efficient work — an electrician, plumber, and drywaller can all work independently because the frame provides a shared reference structure. The metaphor transfers this double nature: a conceptual framework constrains what you can think or build, but that constraint enables collaborative and efficient work within the established structure.
- Standardization over custom — residential framing uses dimensional lumber at standardized spacings (16 or 24 inches on center). This convention allows any carpenter to work on any frame, any inspector to evaluate any structure, and any material supplier to stock the right sizes. The metaphor imports this: frameworks derive their value from being shared conventions, not from being optimally designed for any single use case. A framework used by one person is a personal preference; a framework used by a thousand is infrastructure.
- The frame disappears — in a finished building, the frame is hidden behind drywall, siding, and finish. Occupants interact with the frame’s consequences (room sizes, window locations) without ever seeing the frame itself. The metaphor transfers this invisibility: a conceptual framework shapes thinking without being visible in the resulting thoughts. A programmer using Django does not see the framework in the rendered webpage. A policy analyst working within a regulatory framework produces documents that reflect the framework’s constraints without naming them.
Limits
- Frames are permanent; frameworks are not — a building’s frame is essentially permanent for the life of the structure. But conceptual, software, and organizational frameworks are routinely replaced. Companies “migrate” from one software framework to another; academic fields abandon one conceptual framework for a rival. The metaphor imports a permanence that discourages framework change: it makes switching frameworks feel like demolition when it may be more like renovation. This false permanence can trap organizations in outdated frameworks because “changing the frame” sounds structurally catastrophic.
- Frameworks are not neutral scaffolding — the metaphor implies that a framework merely supports whatever you want to build within it. But frames have opinions: a building framed for a ranch house cannot become a cathedral without new framing. Similarly, a software framework designed for request-response web applications makes real-time streaming awkward. A strategic framework built around competitive advantage makes cooperative strategy hard to express. The frame does not merely support content — it actively shapes what content is possible, natural, and awkward.
- The choice of framework is itself a decision — in construction, framing is dictated by building codes, site conditions, and established practice. There is rarely a “framework choice.” But in intellectual and software contexts, the choice of framework is itself a high-stakes decision that the metaphor treats as a preliminary step. “First, let’s establish a framework” sounds like sensible preparation, but the framework choice may be the most consequential decision in the entire project — a decision the metaphor encourages you to make quickly so you can get to the “real work.”
- It obscures the foundation — a frame sits on a foundation, which the frame metaphor treats as given. But in practice, what sits beneath the framework (assumptions, values, data sources, funding structures) is often more important than the framework itself. The metaphor focuses attention on the visible structural choices while the foundation — the assumptions that support those choices — remains unexamined.
Expressions
- “Conceptual framework” — the academic standard, meaning the organizing structure for a theory or research program
- “Software framework” — a pre-built structure that developers fill in with application-specific code (Rails, Django, React)
- “Regulatory framework” — the structure of rules within which regulated entities operate
- “Strategic framework” — the organizing structure for an organization’s strategic decisions
- “Let’s establish a framework first” — the procedural move to define structure before content
- “Within the framework of” — the spatial preposition that reveals the metaphor’s containment logic: frameworks are things you work inside of
- “Reframe” — the meta-operation: changing the framework itself rather than working within it
Origin Story
“Framework” entered English in the 14th century as a literal description of the wooden frame of a building. The figurative extension — a structure that organizes and supports non-physical content — appeared by the 17th century. The word’s extraordinary productivity across domains (philosophy, law, software, management, education, policy) reflects the structural fitness of the building-frame metaphor for describing organizational structures. The metaphor is so thoroughly dead that “framework” now functions as a near-synonym for “organized approach,” with no residual awareness of the carpentry source.
In software engineering, the specific sense of “framework” (a library that inverts control, calling your code rather than being called by it) emerged in the 1980s and 1990s. This sense is structurally closer to the carpentry source than the generic usage: a software framework, like a building frame, provides the fixed structure that you fill in with your specific content, and it constrains the shape of what you can build.
References
- Kuhn, T. The Structure of Scientific Revolutions (1962) — the paradigmatic use of “framework” in the philosophy of science
- Gamma, E. et al. Design Patterns (1994) — the software engineering context where framework acquired its specific technical meaning
- Johnson, R. and Foote, B. “Designing Reusable Classes” (1988) — early articulation of the framework concept in object-oriented design
Related Entries
Structural Neighbors
Entries from different domains that share structural shape. Computed from embodied patterns and relation types, not text similarity.
- Flexible Office Space (architecture-and-building/pattern)
- Cyberspace Is a Place (spatial-location/metaphor)
- Potential Space (spatial-location/metaphor)
- Holding Environment (containers/metaphor)
- Psychological Safety (psychology/mental-model)
- Window (embodied-experience/metaphor)
- File Permissions (governance/metaphor)
- Facilitating Environment (organism/metaphor)
Structural Tags
Patterns: containerpart-wholeboundary
Relations: containenable
Structure: hierarchyboundary Level: generic
Contributors: agent:metaphorex-miner