Give feedback in plain terms, not code terms

When something's wrong with a tool, I describe the problem the way I'd describe it to a coworker, not in code terms I don't actually know. "The list shows the wrong name" works better than guessing at technical language.

Plain feedback is honest feedback. Trying to sound technical when you're not can send a coding session chasing the wrong fix entirely, wasting a whole session on a guess instead of the real issue. Describing exactly what you saw, and exactly what you expected instead, gives the tool everything it needs to find the actual cause, without you pretending to know more than you do.

Try this today: the next time something looks wrong, write down exactly what you saw and exactly what you expected in plain sentences, and hand over nothing more than that.