The WyCash Portfolio Management System.

Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA '92 Addendum to the Proceedings, 29-30.

Type

Conference paper

Intellectual base

Primary research

Year

1992

DOI

10.1145/157709.157715

Link

https://doi.org/10.1145/157709.157715

Cited from

biology_ecology, computer_science, economics_finance, engineering_design, marine_science, systems_cybernetics

Cited by

10 citations across 10 artifacts.

Each citation links to the sentence it supports in the citing article.

Primes

• Accumulation
  • In organizations and policy, technical debt, regulatory accretion, and institutional memory accumulate from flows of decisions and resist instantaneous correction.

    This sourceCoins the technical-debt metaphor, framing accreted shortcuts in a codebase as an accumulated stock that grows from a flow of expedient decisions and resists instantaneous correction.

• Biofouling
  • Software engineering: long-lived codebases accumulate unreferenced functions, dead configurations, deprecated tests, and stale comments, each individually reasonable when added, collectively raising maintenance drag — technical debt as biofouling on the developer-codebase interface.

    This sourceIntroduces the "technical debt" metaphor: accreted code that is individually reasonable yet collectively raises maintenance and navigation drag on the developer–codebase interface — occupation cost paid for presence, not activity.

• Clearance Rate
  • Toxicological bioaccumulation logic ports to technical-debt accumulation, with the insight that when clearance is slower than input, stock grows linearly with time and cleanup cost is dominated by accumulated stock rather than current input.

    This sourceIntroduces the technical-debt metaphor: unremediated shortcuts accrue 'interest,' so debt accumulates when remediation (clearance) lags creation and cleanup cost grows with the accumulated stock.

• Exaptation
  • Software exaptation is so common that it is frequently the source of technical debt — capability acquired without redesign, at the cost of structures stretched far beyond their original intent.

    This sourceACM. Original "technical debt" metaphor: shipping immature, not-quite-right code buys speed now (visible savings) and is repaid with compounding "interest" later, capturing the benefit-now / cost-later temporal-mismatch dynamic.

• Maintenance
  • Institutional design matters: if maintenance decisions are made by someone who will bear the cost of failure, maintenance is prioritized; if decisions are separated from responsibility for failure, maintenance is deferred—a temporal-mismatch dynamic Cunningham (1992) named "technical debt" in his founding metaphor for compounding deferred-maintenance costs in software.

    This sourceACM. Original "technical debt" metaphor: reframes deferred maintenance as compounding cost incurred today (visible savings) and repaid with interest later (invisible until catastrophic), capturing the prevention-now / benefit-later temporal-mismatch dynamic.

• Path Dependence
  • Computer science & software engineering: Architectural decisions accumulating technical debt (Cunningham, 1992), API stability requirements creating downstream rigidities, programming language adoption and ecosystem lock-in, database schema decisions binding downstream applications, legacy system dependencies that constrain innovation despite clear modernization benefits.

    This sourceACM. Original "technical debt" metaphor: reframes deferred maintenance as compounding cost incurred today (visible savings) and repaid with interest later (invisible until catastrophic), capturing the prevention-now / benefit-later temporal-mismatch dynamic.

• Technical Debt
  • The compounding with growth is the structural engine: as the codebase grows and a second, then a tenth, customer must be supported, the volume of operations passing through the un-isolated data layer rises, so the integrated cost climbs quasi-exponentially, and at the bankruptcy threshold the interest (the cost of working around the assumption on every change) exceeds the cost of paying down the principal (refactoring to true multi-tenancy).

Mechanisms

• Expansion Debt Review
  • It is a direct application of technical debt — the metaphor that shortcuts taken for speed accrue like a loan

    This sourceFrames expedient first-time code as debt whose unrepaid interest slows later engineering work.

• Legacy Health Review Cadence
  • It converts "we integrated the legacy" from a finished event into a maintained state, and it is the natural guard against inherited technical debt

    This sourceFrames initially acceptable implementation shortcuts as debt whose unrepaid interest accumulates into present maintenance cost.

• Technical Debt Register
  • The metaphor it rests on is Ward Cunningham's original technical debt

    This sourceIntroduces technical debt as the loan-like cost of shipping expedient, not-quite-right code.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:bb55574305b3 · see in the full table