2 ms·

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 ne

by t43562 2y ago

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 2y 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?