Tech Debt Eulogy 技术债葬礼

Something is about to be deleted. Write its obituary before it goes — so the decision is recorded, the useful parts are rescued, and nobody has to guess in two years why it disappeared.

Why bother writing this down

Deletions are the least documented events in a codebase. Additions get PRs, commits, and issues. Removals get a one-line commit message and then the knowledge is gone. Six months later someone asks "why don't we support X anymore" and the answer takes a week of archaeology.

The eulogy is a one-page answer to that question, written while the person who knows is still here.

Workflow

1. Reconstruct the life

Pull real dates from git — do not estimate.

# when it was born
git log --reverse --format='%ad %h %s' --date=short -- <path> | head -1