Technical Debt Is a Change Tax You Can Name

Sat, 01 Jun 2019 00:00:00 +0000

A retained compatibility change introduced a contract version and a measured fallback lookup. Related work made acquisition atomic, separated expiration from wall-clock dates, narrowed compatibility fields, enforced authorization, and protected unselected drafts.

That history proves several rules had to become explicit. It does not prove that the old design charged technical-debt interest. The changes might be planned slices, newly discovered requirements, corrections, or work a different design would also need.

Planning on Brian Faust

Technical Debt Is a Change Tax You Can Name