I’ve been building an app with Claude as my coding helper. Yesterday it broke - users couldn’t see their data. I asked Claude to fix it. Claude saw “too many requests” errors in the logs and decided that was the problem. It made 4 different fixes. Each one shipped cleanly. None of them actually fixed the bug. The real issue was something completely different - a library we use changed how it labels stuff, and our app was still reading the old labels. So every piece of data came back blank. My teammate found it in 30 minutes by literally printing out one piece of data and going “wait, why is this empty?” When I asked Claude later why it missed this, the honest answer was: it locked onto the first thing that looked like a cause and never questioned it. It never did the simplest check - look at one piece of the data first and ask “does this even make sense?” The lesson: AI is really good at solving problems you point it at. It’s bad at picking which problem to look at. If I had said “first check if the data even looks right before assuming it’s a network issue,” it would have caught the bug fast. My new rule for any “stuff isn’t showing up” bug: look at ONE piece of the broken data first. Then start guessing. TL;DR: AI will fix the wrong thing very efficiently if you don’t tell it what to verify first. submitted by /u/SadNose6889
Originally posted by u/SadNose6889 on r/ClaudeCode