6 ms·

Also related: https://blog.codinghorror.com/commandos-infantry-and-police/ https://blog.codinghorror.com/commandos-infantry-and-police/ I work a lot in the tra

Also related: https://blog.codinghorror.com/commandos-infantry-and-police/ https://blog.codinghorror.com/commandos-infantry-and-police/ I work a lot in the transition area between commando and infantry aka X_10 and TEAM. I’ve also found myself on TEAM++ coming in to replace TEAM. It is difficult to explain to customers that SVC was built on a set of assumptions which I turn informed the design. Once the assumptions changed then design typically needs to change as well.

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?