Kris McDaniel

This Is Metaphysics


Скачать книгу

too. If you have objections to an argument discussed, jot those down too. The third time you read the chapter, read it with the goal of finding answers to the questions you wrote down. Check to see whether any guesses you made have been confirmed or refuted. There is no guarantee that you will have all of these answers by the third read, but you should have a much clearer understanding of the issues discussed. In short, my recommendation is that you read through this book at three least times: first as a tourist, second as a detective, and third as a judge who compels the witnesses to answer your questions.

      0.5 I will occasionally raise questions that I do not attempt to immediately answer. When this happens, I invite you to pause and consider these questions before reading further. How might answering them one way rather than another affect the arguments you are considering?

      0.6 I have tried to make this book as accessible as I can. This is why I have made an effort to minimize the use technical jargon. But occasionally the introduction of technical terminology is important, and so sometimes I introduce some. My view on technical jargon is this: in every field, whenever it is feasible to avoid using technical phrases and stick instead to ordinary words, this is what you should do. Technical jargon should be viewed as a necessary evil, and like all necessary evils, it should be tolerated only when genuinely necessary, or at the very least, only when it is too cumbersome or annoying to do without it.

      0.7 There are three situations in which it is a good idea to introduce technical jargon. First, sometimes using technical terminology lets you avoid writing out the same complicated sentences over and over again. In short, when you need an abbreviation, a bit of technical jargon can be useful. Here’s a paragraph in which the introduction of some technical terminology would have been very helpful:

      What a cumbersome paragraph to read! (It wasn’t much fun to write either.) Even if the argument contained in this paragraph is a great argument, it is really hard to figure out what that argument is because you have to keep reading the same long chunk of words. Some way of abbreviating that long chunk would help. To see this, check out this paragraph:

      A lot of people want to know what makes a life worth living. Some people think that a person’s life is worth living if and only if that person experiences a greater amount of pleasure than pain throughout the course of her life, and that a life is better or worse to the extent that the balance of pleasure over pain is higher or lower. Let’s call this theory hedonism. I think that hedonism is a false theory. Here is an argument against hedonism. Suppose there is a person who spends the entirety of his life isolated from other human beings, acquires no interesting knowledge, and participates in no worthwhile activities, but derives a lot of pleasure from scratching himself. This person never experiences any pain. This person has a life that is barely worth living—few of us would switch places with him because we correctly think that our life is a better life. But hedonism implies that this person has a great life. So, hedonism is false.

      I trust that you see that the second paragraph is much easier to read and understand because I introduced a bit of technical jargon, specifically, the word “hedonism.” So sometimes technical terminology is necessary (or at least extremely helpful!) because it serves to abbreviate. But the jargon will be useful only if you also commit to remembering what that jargon abbreviates. So, when you come across any technical jargon, please commit yourself to remembering what it means! It will make your trek through this book more straightforward. (That said, there is a glossary at the end of the book that you may consult if you forget.)

      0.9 There’s a third reason to introduce technical jargon, but I am going to ask that you wait until Section 2.10 to think about it. I promise I will talk about it there.

      0.10 In general, when I introduce a word or phrase that is being used in a technical sense, I will italicize the first use of that word and then provide an explicit technical definition. And, as I mentioned earlier, it’s a good idea to memorize the technical jargon when it first appears so you don’t waste precious brain power remembering definitions when you should be working through philosophical puzzles.