3 ms·
> often in the form of production outages Completely unrelated. If you have production outages resulting from new code you have serious gaps in your certificat
by austincheney 6y ago
> often in the form of production outages
Completely unrelated. If you have production outages resulting from new code you have serious gaps in your certification process, especially so if the new code covers existing process/requirements. You are probably insecurely reliant upon dependencies to fill gaps you haven’t bothered to investigate, which is extremely fragile.
The benefit of code reuse is simplification. If a new problem emerges with requirements that exceed to current simple solution you have three choices:
1. Refactor the current solution, which introduces risk.
2. Roll an alternative for this edge cases and refactor after. This increases expenses but is safer and keeps tech debt low.
3. Roll an alternative for this edge case and never refactor. This is safe in the short term and the cheapest option. It is also the worst and most commonly applied option.
- clooless 6y ago> If you have production outages resulting from new code you have serious gaps in your certification process If you have production outages every week, yeah. But no organization is free of production outages. When they do happen (I said when, not if) it matters a lot if you used standard libraries, code that is plugged into the infrastructure, and the like, and not hand-rolled cowboy code
- austincheney 6y ago> it matters a lot if you used standard libraries Why? From a security perspective, an outage is a security matter, the remediation plan is what’s important.