Lesson 3. Reasoning Without Tripping Over Your Own Argument

Last lesson gave you the historian's questions for weighing evidence. This one gives you the rules for handling an argument without tripping over it yourself. By the end you will be able to separate a premise from a conclusion, tell valid from sound, name four common fallacies, and say exactly what a fallacy does and does not prove.

An argument has premises — the reasons offered — and a conclusion, the claim those reasons are meant to support.

Being able to separate them is often the whole job. Many disagreements simply dissolve once both sides can say out loud which statement is doing the supporting and which is being supported. Until then, two people can argue for an hour about different things.

Deductive arguments aim to guarantee the conclusion: if the premises are true and the form is good, the conclusion must follow.

Inductive arguments aim to make the conclusion probable. They can be very strong without being airtight.

Most historical reasoning is inductive. That is exactly why a demand for proof in this area is misplaced — it asks history to behave like arithmetic.

Two words worth keeping straight for life.

An argument is valid when its form is good. It is sound when it is valid and its premises are actually true.

So a perfectly valid argument built on a false premise is worthless. Knowing which of the two is under dispute tells you which reply to make: attack the form, or attack the premise. Attacking the wrong one wastes the whole exchange.

Ad hominem. Rejecting an argument by attacking the person making it. Facts about a speaker are usually irrelevant to whether the reasoning works. A rude person can be right; a kind person can be wrong.

Straw man. Restating an opponent's view in a weakened form and then defeating that. The real position is untouched — and anyone who knows the real position will discount everything else you say.

False dilemma. Presenting two options as if they were the only options. This is common in discussions about what people believe, where several positions are usually available, not two.

Genetic fallacy. Judging a claim by where it came from rather than by the evidence for it. Notice that this one cuts both ways: a claim is not false because it appears in a religious text, and it is not false because it appears in a secular one.

Consider this argument: this book is true because the book says it is true.

The argument is circular — the conclusion has been smuggled into the premise — so it fails. The fault is not in its form, which can be perfectly valid; it is that the argument gives a listener no reason they did not already have.

Now notice exactly what has and has not been shown.

A fallacy is a defect in an argument. It is never a disproof of the conclusion. A true claim can be defended badly. Pointing out that one argument for a claim is circular leaves the claim itself exactly where it was — still open, still to be settled by better evidence.

That distinction is the reason the units ahead exist at all.

Christians have historically argued from outside evidence — manuscripts, non-Christian writers, testimony, ordinary historical reasoning — precisely so that the case does not rest on a text's claim about itself.

So if someone shows you that one of your arguments is circular, the right move is to thank them and reach for a better argument. Defending the bad one is how you lose ground you did not have to lose.

The principle of charity says: interpret the other person's argument in its strongest reasonable form before you reply.

This is a reasoning discipline, not politeness. Answering the strongest version is the only way to find out whether your own position actually survives. And a reply that defeats only a weak version convinces nobody who knows the strong one.

The burden of proof falls on whoever makes a claim — and this runs in both directions.

Someone who asserts that the accounts were fabricated has made a positive claim and picked up a burden with it. They are not merely asking questions, however the sentence is phrased. Saying so calmly, once, is fair; saying it repeatedly is a dodge.

Here is a practical test for everything ahead. Can you state the opposing view so accurately that someone who holds it would say, "yes, that is what I think"?

If you cannot, you are not ready to answer it yet. Go and find the strong version first.

Try this fresh case. Your friend says: "Mr. Kim wants us to read more books, and Mr. Kim is boring, so reading more books must be boring too." Find the premises and the conclusion first.

Premise one: Mr. Kim wants you to read more. Premise two: Mr. Kim is boring. Conclusion: reading more books is boring.

Now test it. Even if both premises are true, does the conclusion follow? No. A boring person can recommend something interesting. This argument is not valid — the form does not connect the premises to the conclusion — so it does not matter whether the premises are true. That is one thing this lesson's tools let you spot immediately: a bad connection, independent of whether the parts are true.

Notice you did not need to know anything about books to catch the problem. You only needed to check whether the conclusion actually follows from what came before it.

That is the whole point of testing form separately from content. It lets you catch a broken argument even on a subject you know nothing about yet.

Separating premises from conclusions, and testing validity before truth, works because it splits one big question into two small, answerable ones: does the reasoning connect, and are the starting points true?

What this method shows: it can catch an argument that sounds persuasive but does not actually hold together, even before you argue about the facts inside it.

What it does not show: spotting a bad argument for a claim does not show the claim is false. Remember the fallacy rule from this lesson — a fallacy is a defect in the argument, never a disproof of the conclusion. Mr. Kim's recommendation might still be great, even though the argument against it was bad.

So the two-step habit is: check the form first, and if it fails, go looking for a better argument rather than treating the conclusion as settled either way.

Someone might push back: "This all sounds like a trick to win arguments. Isn't naming fallacies just a way to shut people down?"

That worry is worth taking seriously, because fallacy-spotting can be used that way, and that would be a misuse.

Here is the honest reply. These tools are not a shortcut to winning; they are a discipline for getting closer to the truth, and the principle of charity is built into this same lesson to stop it from becoming a game. You are required to state the other person's argument at its strongest before you touch it. Named correctly, a fallacy is not "gotcha" — it is "here is the exact spot the reasoning breaks, so let's fix it and find a better argument together."

Say each term out loud, then use it in one sentence about this lesson.