Technique

Show It

Some things are hard to describe in words. Upload an image instead — AI can see it.

See the Difference

One tries to describe an error. The other just shows it.

Described in words
You: "I'm getting an error in my app. It's a red box with some text about a null reference, and there's a stack trace below it. The error appears when I click the submit button. The line number mentioned is 247 but I'm not sure which file."

AI: A null reference error typically means you're trying to use an object that hasn't been initialized. Can you share the exact error message? What does line 247 look like? Which file is it in?

AI needs more information. Back and forth begins.

Showed a screenshot
You: "What's causing this error?" [+ screenshot of error message]

AI: The error shows a NullReferenceException in UserService.cs at line 247. The stack trace indicates it's happening in the GetUserById method when the database returns null. You need to add a null check before accessing user.Email on that line.

AI sees exactly what you see. Immediate, specific help.

Why This Works

Words have limits. Try describing the exact layout of a broken UI, the shape of a chart trend, or the specific elements in an error message. You'd spend a paragraph explaining what a screenshot shows in a second.

Modern AI can see images — screenshots, diagrams, photos, handwritten notes, whiteboard sketches. When something is visual, show it.

What You Can Show

The Technique

When describing something feels awkward or incomplete, upload an image instead. AI sees what you see.

When to Use This