Re:A Theory of Software Architecture
by berkes on Wednesday October 28, 2020 @04:03AM
(#24916372)
Or, how I would put it more pragmatic: the first example is a sure way towards seven slightly different mechanisms to call an Api. Per year. On a team with seven devs.
[ Parent
| on HN ]
Not doing the first example is a sure way towards either copying that function and changing it a bit because you need a slightly different call, or a function with a pile of branches in it because it needs to operate in several modes.
Both ways could go wrong. I don't care what your architectural choice is, you can still mess it up.