3 ms·
I'm dealing with one internal project where this happens because there's an artificial IT/build distinction between "emergency" code push and "casual" raw datab
by Terr_ 10y ago
I'm dealing with one internal project where this happens because there's an artificial IT/build distinction between "emergency" code push and "casual" raw database change.
This means lots of business-rule crap gets softcoded into the database or ini files (increasing complexity and bug-risk) just to support a hypothetical future where somebody needs it changed without a full sprint cycle.