Software is considered "fragile" when issues or changes in one part of the system can have side-effects in conceptually unrelated parts of the codebase.
Fragile software tends to break easily and may be challenging to maintain.
Building an anti-fragile system requires careful thought and consideration outside of the scope of this review.
In general, prioritize the following concepts:
- Follow the single-responsibility principle of functions
- Reduce reliance on external systems
- ConsenSys Audit MCDEX V2 Finding 2.3
- Fragile Code
- System Side-effects
- Interdependence
- Function Purpose
- Reduce Dependence