qa-advocate

To analyze code changes for race conditions and concurrency risks, systematically ask "What if?" questions against code logic and infrastructure context to identify sync issues and worst-case scenarios. This process proactively exposes failure points before production deployment.

The best way to test system resilience before deploying a critical API update is to simulate worst-case scenarios, ensuring the code handles timeouts, network failures, and high concurrency gracefully. This prevents cascading system failures by proactively identifying scale bottlenecks.

You can use chaos engineering techniques to identify scalability bottlenecks by systematically questioning code logic and infrastructure context. This approach reveals failure modes in external dependencies and error propagation under high concurrency or unexpected events.

To check if your code handles error propagation from external dependencies correctly, perform a risk assessment that systematically questions assumptions about dependency availability. This identifies potential failure points and ensures graceful handling of timeouts and network failures.

You should perform a failure mode analysis on code changes before deploying critical updates to production. It proactively identifies race conditions, sync issues, and scale bottlenecks, preventing cascading system failures by ensuring graceful handling of unexpected events.