3 ms·
Quite and very much this. Where the change is needed and previous rationale can't be determined, if possible: - Note that you've made the change. - That the
by dredmorbius 5y ago
Quite and very much this.
Where the change is needed and previous rationale can't be determined, if possible:
- Note that you've made the change.
- That the previous rationale wasn't clear.
- If possible, provide for backing out the change if it proves ill-advised.
Often an initial approach can be to disable or bypass a specific mechanism. E.g., put a gate in a fence, a bridge over a gap, disable a feature, etc. Watch to see what does or doesn't fail.
In software, specific time-triggered events may exercise infrequently-traversed paths --- end of week, month, year, etc. Naturally, these are hard to detect in advance. More convoluted are conditions triggered rarely (lunar cycle ~= 19 years, leap years, Unix epoch overflows, etc.).
This is where documentation and QA engineering will save butts.