systems-thinking

Blast radius analysis evaluates how a change impacts callers, consumers, and sibling implementations rather than just the modified lines. This framework identifies all downstream dependencies that require updates to maintain system consistency.

Systems thinking in software architecture is a reasoning framework for evaluating changes against established conventions. You need it during research, design, planning, and implementation to prevent broken dependencies and technical debt from isolated changes.

Enforce coding conventions by applying a reasoning loop that validates new code adheres to established naming, layout, and error-handling patterns. This ensures all co-changing surfaces are addressed within the same slice.

Refactoring breaks downstream consumers when changes are implemented in isolation, ignoring broader system context. A reasoning framework identifies all sibling implementations and dependent surfaces that must be updated simultaneously.

Yes, architectural reasoning validates code review changes by evaluating proposed modifications against existing system architecture. It operates during implementation to confirm all co-changing surfaces are addressed within the same development slice.

Evaluating code changes in isolation leads to broken dependencies, inconsistent patterns, and technical debt. Without analyzing the blast radius, you miss downstream consumers and sibling implementations that require concurrent updates.