---
id: "concept-archaeological-programming"
type: "concept"
source_timestamps: ["00:09:45", "00:10:00"]
tags: ["software-engineering", "technical-debt"]
related: ["concept-vibe-coding", "entity-addy-osmani"]
definition: "The process of having to reverse-engineer and excavate an opaque, AI-generated codebase because it was built without deep human understanding."
coined_by: "Addy Osmani"
sources: ["s25-builders-identity-shift"]
sourceVaultSlug: "s25-builders-identity-shift"
originDay: 25
---
# Archaeological Programming

## Definition
The process of having to reverse-engineer and excavate an opaque, AI-generated codebase because it was built without deep human understanding.

## Origin
The term was coined by [[entity-addy-osmani]], Google Chrome engineering lead, in 2024 writings on AI code debt from rapid generation without review.

## How It Forms
When a codebase is built entirely through high-speed [[concept-vibe-coding]] without deep human comprehension, the resulting system is **functional but opaque**. The code was generated rapidly by AI and accepted without review.

## The Excavation Burden
Future developers — or even the original creator a few months later — must act as **archaeologists**, carefully excavating and reverse-engineering the codebase just to understand:
- How it works
- Why certain decisions were made
- How to safely modify it

## Relation to Other Debts
It represents a severe form of technical debt that compounds with [[concept-experiential-debt]]. Both are central to the argument in [[claim-vibe-coding-debt]].

## Mitigation
Pair every burst of [[concept-vibe-coding]] with [[concept-strategic-deep-diving]] (see [[action-shift-altitude]]) and [[concept-temporal-separation]] (see [[action-reflect-mode]]) to prevent comprehension loss.


## Related across days
- [[concept-vibe-coding]]
- [[claim-vibe-coding-debt]]
- [[question-legacy-brownfield-migration]]
- [[concept-experiential-debt]]