← sources

How do you pinpoint a large codebase to know exactly where to make changes, when AI is just not giving the desired results?

source: reddit (reddit:developersIndia)published 2026-10-21 17:12ingested 2026-10-22 02:38

retained text

Sometimes, a particular feature isn’t producing the quality of results I want, and I need to figure out exactly where the problem lies. 

Simply asking AI to investigate and fix it isn’t working reliably. 

I feel like I need to understand the code myself, trace how data flows through the application, identify the relevant functions, and figure out what needs to change. But in a large codebase, I often don’t know where to start or how to narrow things down.

For experienced developers, how do you approach this in practice?

How do you go from observing a problem to identifying the specific function or module responsible? or you just ask claude do it. 

What tools or techniques do you use to trace execution and data flow?

How do you combine AI coding tools with your own debugging and code investigation?

Help me to not be a vibe coder. 

document fetched 2026-10-22 00:25 · canonical https://reddit.com/r/developersIndia/comments/1xbt3p3/how_do_you_pinpoint_a_large_codebase_to_know