If your application has a bug that you cannot reproduce reliably, unexpected behavior, crashes, broken business logic, inconsistent data, API failures, synchronization issues or a problem that keeps returning after previous fixes, I can investigate the underlying cause instead of only patching the visible symptom.

My goal is to understand why the problem occurs, identify its root cause and implement an appropriate solution while minimizing unnecessary changes to the existing system.

• Application crashes and unexpected exceptions • Incorrect or inconsistent application behavior • Business logic errors • State management problems • Authentication and authorization failures • API and backend errors • Database inconsistencies • Data synchronization problems • Offline/online synchronization issues • Race conditions and intermittent failures • Third-party API integration failures • Incorrect calculations or data transformations • Performance-related problems • Memory-related issues • Broken navigation or application flows • Deployment and production issues • Technical debt contributing to recurring bugs • Problems introduced by previous changes or migrations

I review the expected behavior, actual behavior, reproduction steps, logs and any relevant technical context.

When possible, I reproduce the problem locally or in the provided environment to establish a reliable baseline.

I trace the relevant flow through the application, including UI/state, business logic, APIs, services, databases and external dependencies when necessary.

I determine which component, interaction, assumption or implementation decision is actually responsible for the problem.

I apply the smallest appropriate change when possible rather than introducing unnecessary rewrites.

I test the affected functionality and related flows to reduce the chance of introducing regressions.

I can provide a concise explanation of the root cause, what was changed and any relevant recommendations for preventing similar issues.

A simple UI or logic issue may require only a small targeted fix, while a deeper issue may involve multiple layers of the system, database changes, architectural refactoring, migration or redesign.

For large, unclear or high-risk problems, I may recommend starting with a paid diagnostic phase before quoting the complete implementation.

• Source repository or relevant source files • Error messages and logs • Reproduction steps, when available • Expected vs. actual behavior • Development environment/setup information • Relevant configuration • Access to required services or staging environments • Information about recent changes that may be related to the issue

Important: I do not need you to already know the root cause. Describing the symptoms and expected behavior is often enough for me to begin the investigation.

For security, confidentiality or access reasons, credentials and secrets should never be shared through plain text. Temporary access or appropriate environment-specific credentials are preferred.