This is a major issue. Why the code is what it is. You need a history of the ass... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		t43562 8 months ago \| parent \| context \| favorite \| on: Software Design Is Knowledge Building This is a major issue. Why the code is what it is. You need a history of the assumptions so that new developers can know what's legacy and what isn't. I've never yet had a set of requirements that didn't change.

CRConrad 8 months ago [–]

> You need a history of the assumptions so that new developers can know what's legacy and what isn't.

Isn't this (at least in part (and perhaps only approximately)) what Architecture Decision Records are for?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact