Locked learning resources

Join us and get access to thousands of tutorials and a community of expert Pythonistas.

Unlock This Lesson

Locked learning resources

This lesson is for members only. Join us and get access to thousands of tutorials and a community of expert Pythonistas.

Unlock This Lesson

Habits for Checking Results

An agent can do the arithmetic perfectly on the wrong data. Imagine you ask for a summary of your team’s expenses in September, and the agent goes by the date each booking was made when the card statement goes by the date it was charged. Every sum is correct, and the total still doesn’t match the statement. Of the four questions from When the Result Is Wrong: Four Questions, this is a what was it given problem.

Now imagine you ask whether your team is keeping up with its weekly sales target, and the agent compares a whole month of sales against that weekly target. The figures are real, but the comparison is off, so the team looks as if it’s selling about four times its target. That’s a what was asked problem, because the agent answered a question nobody meant to ask.

If you checked a single number against a source you trust, you’d catch both mistakes.

Confident and Wrong

A wrong answer reads just as smoothly as a right one. Because a model writes what’s likely, it produces clear, sure-sounding text whether or not anything was checked, so a confident tone tells you nothing about whether the answer is correct. A reply can name a web page that doesn’t say what the reply claims, or report a total that was never added up, in the same calm voice it uses for everything else.

Locked learning resources

Join us and get access to thousands of tutorials and a community of expert Pythonistas.

Unlock This Lesson

Already a member? Sign-In

Locked learning resources

The full lesson is for members only. Join us and get access to thousands of tutorials and a community of expert Pythonistas.

Unlock This Lesson

Already a member? Sign-In

00:00 Habits for Checking Results.

00:03 An agent can do the arithmetic perfectly on the wrong data. Imagine you ask for a summary of your team’s expenses in September. The agent goes by the date each booking was made.

00:13 But the card statement goes by the date it was charged. Every sum is correct, and the total still doesn’t match the statement. Of the four questions, this is a problem with what it was given.

00:24 Now imagine you ask whether your team is keeping up with its weekly sales target. The agent compares a whole month of sales against that weekly target. The figures are real, but the comparison is off.

00:37 So the team looks as if it’s selling about four times its target. That’s a problem with what was asked, because the agent answered a question nobody meant to ask.

00:46 If you checked a single number against a source you trust, you’d catch both mistakes.

00:52 A wrong answer reads just as smoothly as a right one. A model writes what’s likely. So it produces clear, sure-sounding text, whether or not anything was checked.

01:02 A reply can name a web page that doesn’t say what the reply claims. It can report a total that was never added up. And it uses the same calm voice it uses for everything else.

01:13 Four habits help you catch problems like these, before you rely on the result. First, ask what kind of can’t it is. When an agent says it can’t do something, ask whether that’s truly impossible, or only impossible with the tools it has.

01:27 An agent can only use the tools its app gives it. Second, ask to hear about blockers. An agent that can’t reach something may work around it without telling you, and give you a weaker answer.

01:39 So say up front that you want to know when it gets stuck. You might be able to give it what it needs.

01:45 Third, treat a number as a claim until you’ve checked one. Agents can pick up the wrong data, or misread a table. They can slip in the arithmetic, too. Spot-checking a single figure doesn’t take long.

01:57 Fourth, keep notes on where results came from. Ask the agent to note which files, dates, and web pages it used. Keep that note with the result, so you can check it or redo it later.

02:09 Sources deserve a check of their own. When an answer states a fact, ask where it came from. An AI can invent sources that look real, down to a title, an author, and a link.

02:20 So open the source and check two things. Does it exist? And does it say what the AI claims? Apps that search the web give you real links. But their summary of what a page says can still be wrong.

02:33 So a confident tone tells you nothing, and one checked number tells you a lot. Below this video, you can question an agent about its September expense total.

02:42 Find all four problems, using as few follow-ups as you can. Then read why the two most natural follow-ups find nothing.

Become a Member to join the conversation.