site banner
felipec  unbelief  2yr ago (felipec.substack.com)   3600 thread views

2+2 = not what you think

felipec.substack.com

Changing someone's mind is very difficult, that's why I like puzzles most people get wrong: to try to open their mind. Challenging the claim that 2+2 is unequivocally 4 is one of my favorites to get people to reconsider what they think is true with 100% certainty.

-34
Top Bottom Old Controversial Comments
Jump in the discussion.

No email address required.

It does matter what you call it

I did not say it doesn't matter what I call it, I said it doesn't matter what you call it.

And it seems pretty clear to me you are being intentionally obtuse. The purpose of me communicating to you is that you understand what I mean, it doesn't matter how. For any given idea I have there's a set of words I could use to transmit that idea, and any word I use has multiple meanings, but as long as you pick the meaning that correctly match the idea I want to transmit, we are communicating effectively. The "most common meaning" is completely irrelevant. The most common meaning of the word "get" is "to gain possession of", but if I say "do you get what I mean", I'm not using the most common meaning, and I don't have to.

I used multiple words, terms, and an explanation for you to understand what I meant, and if you understand it, I don't personally care what word you use to name that idea.

To assume(everyday) something means approximately to act as if that something were true, without feeling the need to personally verify it for oneself.

To assume(logic) something means to accept it as an axiom of your system (although potentially a provisional one) such that it can be used to construct further statements and the idea of "verifying" it doesn't make much sense.

I don't see the any difference. If you "assume X" it means you hold X as true without any justification, evidence, verification, or inference.

In other words, even though he didn't assume(logic) that 1+1=2, his assumption(everyday) that 1+1=2 would be so strong as to reverse all the logical implication he had been working on

I disagree. Every day he saw evidence that 1+1=2, so it would be reasonable to believe (not assume) that this was always true. Additionally he saw no way it could not be true, but he was rational enough to know this was not a good reason to assume it was true, as this would have been an argument from incredulity fallacy.

Maybe he did assume that 1+1=2 in everyday life, but you cannot know that unless you could read his mind.

This is a converse error fallacy. If I assume a chair is sound, I would sit down without checking it, but if I sit down without checking it doesn't necessarily mean I assumed it was sound.

In general rationalists try to not assume anything.

If I'm wrong about any of those I will be happy to be corrected.

I know helloworld is a nearly useless program in the vast majority of contexts, but not all, and I know that people frequently practice new programming languages by writing programs in them with little regard for the practical use of those programs, but not all people who write helloworld programs are practicing new programming languages.

You are assuming the general case. I can easily imagine somebody in the 1970s developing for a new hardware architecture for which there are no other compilers available trying to test that any software runs, in fact, I can even imagine somebody today doing that for a new hardware architecture like RISC-V.

And once again the point of these examples is not to "deliberately wasting people's time", it's to show they are making assumptions even if they can't possibly see how they could be making an assumption.

Every time I tell somebody that they are making an assumption they disagree, and every time I point to them the assumption they were making they come with a rationalization, like "you tricked me", or "that's very unlikely", or "everyone would have assumed the same". It's never "actually you are right, I didn't think about that".

I don't see the any difference. If you "assume X" it means you hold X as true without any justification, evidence, verification, or inference.

As I've seen the term used outside of logic, it only requires a lack of effort towards verification. You can have justification, evidence, or inference, as long as they are simple enough and easily-enough available. For example, I would find nothing unusual in a drive-by reply to this line consisting of the following sentence: I assume you didn't read the post very thoroughly, then, because the paragraph immediately below where your quote ends contains a distinguishing case.

You are assuming the general case.

Ah! I see the false assumption was "that you are intelligent enough to comprehend those kinds of comparative asides and familiar enough with conversational English to understand that loading them with caveats would draw too much focus away from the point they are supporting." Asides of that type are implicitly restricted to the general case, because they are intended to quickly illustrate a point by way of rough analogy, rather than present a rigorous isomorphism.

I assume you didn't read the post very thoroughly, then, because the paragraph immediately below where your quote ends contains a distinguishing case.

This is an equivocation fallacy. You are using a different definition of "assume", in particular using it exactly as "suppose". In my view assuming and supposing are two different things, even in the colloquial sense.

I see the false assumption was "that you are intelligent enough to comprehend those kinds of comparative asides and familiar enough with conversational English to understand that loading them with caveats would draw too much focus away from the point they are supporting."

Wrong. I can comprehend the notion without accepting it. This is a converse error fallacy.

Asides of that type are implicitly restricted to the general case, because they are intended to quickly illustrate a point by way of rough analogy, rather than present a rigorous isomorphism.

This is obviously a cop-out. If you were aware that your claim applied only to the general case, but you merely did not make it explicit, then the moment I mentioned there was an assumption you would immediately know what assumption I was talking about, because you were fully aware.

But you didn't know what assumption I was talking about, because you were not aware of the restriction. Now you want to pretend you always knew you were making an assumption, you merely didn't say it when I pointed it out, for some reason.

This is precisely what everyone does. Before they say they aren't making an assumption, and after I point it out to them they always knew. You did exactly what I said people do, and you went for one of the options I listed: "everyone would have assumed the same".

It seems like you don't, actually, understand what that comparative aside was doing, so let me restate it at more length, in different words, with the reasoning behind the various parts made more explicit.

I described a situation where a person generated object A by means of process B, but due to their circumstances the important part of their activity was process B, and object A was important mostly insofar as it allowed the engagement of process B. Since I judged this sort of process-driven dynamic may seem counterintuitive, I also decided to give an example that is clearly caused by similar considerations. Writing Hello World in a new language is a nearly prototypical instance of trivial output being used to verify that a process is being applied successfully. The choice of assembly further increased the relevance of "moderately experienced programmer checking that their build pipeline works and their understanding of fundamentals is correct".

In this context, the existence of the general case - and the fact that it is the typical example brought to mind by the description, as indicated by the name you selected - suffices to serve the purpose of the aside. I did not claim and did not need to claim anything about all instances of building Hello World in assembly; the idea that I was trying to is an assumption that you made.

I did not claim and did not need to claim anything about all instances of building Hello World in assembly; the idea that I was trying to is an assumption that you made.

This is obviously not the case because this was not an aside, but an analogy to another point that you were making. You were clearly saying that a) "coding Hello World in assembly" is never b) "coding Hello World in assembly", and always c) "coding Hello World in assembly", and there was no other possible way to interpret that.

You used that to substantiate your claim that Bertrand Russell didn't actually want to prove 1+1=2, but wanted to do something else using the proof 1+1=2 as a tool.

But in both cases you made assumptions: what you claimed is not necessarily true.

My assessment of you has shifted far enough towards "troll" that I won't bother replying to you again.

Then don't reply, rather taking a parting shot.

What is this place?

This website is a place for people who want to move past shady thinking and test their ideas in a court of people who don't all share the same biases. Our goal is to optimize for light, not heat; this is a group effort, and all commentators are asked to do their part.

The weekly Culture War threads host the most controversial topics and are the most visible aspect of The Motte. However, many other topics are appropriate here. We encourage people to post anything related to science, politics, or philosophy; if in doubt, post!

Check out The Vault for an archive of old quality posts. You are encouraged to crosspost these elsewhere.


Why are you called The Motte?

A motte is a stone keep on a raised earthwork common in early medieval fortifications. More pertinently, it's an element in a rhetorical move called a "Motte-and-Bailey", originally identified by philosopher Nicholas Shackel. It describes the tendency in discourse for people to move from a controversial but high value claim to a defensible but less exciting one upon any resistance to the former. He likens this to the medieval fortification, where a desirable land (the bailey) is abandoned when in danger for the more easily defended motte. In Shackel's words, "The Motte represents the defensible but undesired propositions to which one retreats when hard pressed."

On The Motte, always attempt to remain inside your defensible territory, even if you are not being pressed.


New post guidelines

If you're posting something that isn't related to the culture war, we encourage you to post a thread for it. A submission statement is highly appreciated, but isn't necessary for text posts or links to largely-text posts such as blogs or news articles; if we're unsure of the value of your post, we might remove it until you add a submission statement. A submission statement is required for non-text sources (videos, podcasts, images).

Culture war posts go in the culture war thread; all links must either include a submission statement or significant commentary. Bare links without those will be removed.

If in doubt, please post it!


Rules


Recommended Posts And Communities

Recommended Realtime Chats