Live data from Hacker News

A three-page paper that shook philosophy, with lessons for software engineers

jsomers.net

91–100 of 185 posts

Re: A three-page paper that shook philosophy, with lessons for software engineers

#91
post #20

To me this seems unhelpful. I'd say there is no "knowledge"; there's only belief. And if you defined knowledge as "justified true belief" then you couldn't apply the definition in practice in the real world because you don't know when something is true. But that's philosophy for you: fun (for some people) but not useful.

You assert that there is no knowledge under the expectation that it is true, then you go on and justify it. So it seems you know that there is no knowledge, a contradiction.

Why deny the word has meaning, just because you can't distill it down to a concise explanation? The meaning of a word can be arbitrarily complex. Knowledge can exist, even if you can't define it, because meaning is not determined by definition. Definitions are simply a mechanism for coordinating understanding, not for demonstrating its existence.

Besides, any argument against the existence of knowledge could be used against belief. Play "taboo" with the subject and don't confine yourself to using ancient terminology to describe the world and these pointless linguistic problems melt away.

Re: A three-page paper that shook philosophy, with lessons for software engineers

#92
post #20

To me this seems unhelpful. I'd say there is no "knowledge"; there's only belief. And if you defined knowledge as "justified true belief" then you couldn't apply the definition in practice in the real world because you don't know when something is true. But that's philosophy for you: fun (for some people) but not useful.

We do know when some things are true, and when observing the world we can talk about truth under certain assumptions. As in “it’s True the sun didn’t explode yesterday, assuming we aren’t all living in a simulated reality run by aliens in a different solar system billions of years from now the exact day after the sun exploded, or similar possible scenarios”

And while everyone loves to run in circles around the argument “but how can you know with certainty” the fact is that I am as certain that this assumption holds as I am that it provides no value at all to continually question if reality is really real, you’d have to take that as an assumption to ever have any kind of value adding discussion.

The people who insist we can’t know if anything is definately true must agree that they can’t know if that assertion is definitely true, so they sort of kill their own argument axiomatically.

Re: A three-page paper that shook philosophy, with lessons for software engineers

#93
post #89
post #44

Earlier quoted context omitted.

Yes, i would still classify the software defective. It did not reject backwards explicitly. Just because by accident it works (i.e., the consumer of the output doesn't care) doesn't mean the defect has gone away. To be not defective, the software has to explicitly reject input that it was not designed to handle. Imagine if the software updated with some changes, and the unknown input now produces an incorrect output.…

You could also argue that your expectations are defective. It is possible to accidentally solve a problem in a correct manner.

Not reliably.

It's not professional to design systems that rely on luck.

"Let's ignore this edge case and hope we get lucky" is not something you want to see in a software specification.

Re: A three-page paper that shook philosophy, with lessons for software engineers

#94

I haven't read the original paper, so maybe the example is better, but it seems the cow example fails the justified condition. The knowledge is justified if it derives from the evidence, but once we know the evidence is faulty it can no longer be used for justification by definition. It seems by extension that any justified true belief can become unjustified by the addition of new information that invalidates the jus…

What you're saying is more or less exactly what the paper was getting at.

It's hard to say based on a short Internet comment, but it sounds like the spot where your disagreement comes from is that you're understanding the word "justified" in a slightly different way from how epistemologists were using it. For example, one of the responses to Gettier's paper was to suggest that maybe the definition of "justified" should be altered to include a provision that invalidating the justification would imply that the belief is false.

So, for example, under that modified definition, the visual evidence couldn't serve as a justification of the belief that there is a cow in the field, because it allows the possibility that it isn't a cow but there still is one in the field. On the other hand, it would work for justifying a belief like, "I can see a cow from here." (Yeah, there's another cow in the field, but it's not the one you think you see.) But, still, that wasn't quite the definition that the mid-century epistemologists who made up Gettier's audience were using.

(ETA: Also, the original paper didn't involve cattle at all. Wikipedia has what looks like a good summary: https://en.wikipedia.org/wiki/Gettier_problem#Gettier's_two_...)

Re: A three-page paper that shook philosophy, with lessons for software engineers

#95

I haven't read the original paper, so maybe the example is better, but it seems the cow example fails the justified condition. The knowledge is justified if it derives from the evidence, but once we know the evidence is faulty it can no longer be used for justification by definition. It seems by extension that any justified true belief can become unjustified by the addition of new information that invalidates the jus…

In the example, the subject does not know that the evidence is faulty.

Re: A three-page paper that shook philosophy, with lessons for software engineers

#96
post #51

Earlier quoted context omitted.

Well, why not write them down for us?!

As if they're difficult to derive on one's own? You believe X has cancer because he has the symptoms and you can see an offending black spot on their X-ray. The lab results say the black spot was just a cyst but X indeed has cancer in the same organ.

As in, when u write "I can very easily think of examples in medicine, police work (e.g. regarding suspects), accounting, and so on..." but you don't give any, the natural tendency is not to believe you.

Re: A three-page paper that shook philosophy, with lessons for software engineers

#97
post #48

Earlier quoted context omitted.

In an epistemology class once I said to the lecturer "I don't know anything." He said "Don't you know your name?"

Not good enough, point to that which knows. Where is it? Who knows it? If there is a knower to that, where is it.. Keep going with this investigation and realize there is no knower, only knowing. Eastern philosophy has nailed this thousands of years ago and we westerners are up to this day totally in the dark. We actively treat the I as a concrete object that really exists as an entity. It does not hold any closer ex…

That's really not what epistemology is about at all. (Yes, I'm a big Ramana Maharshi fan etc, I know what you're talking about)

Re: A three-page paper that shook philosophy, with lessons for software engineers

#98
post #40
post #23

Earlier quoted context omitted.

How is 2 & 3 from above different from 4? An unknown input producing correct results is still a problem - the unknown input is the problem. Therefore, i postitulate that anytime an unknown input is possible, the software is defective.

The entire world of AI relies on dealing with "unknown" input?

No, it doesn't. It relies on explicit rules (old school) or statistical inference (new school).

There's a difference between "breaking" unknown input - i.e. non-computable within the system as it stands - and "working" unknown input, which is within expected working parameters.

The latter is business as usual for computing systems.

The former should have a handler that tries to minimise the costs of making a mistake - either by ignoring the input, or failing safe, or with some other controlled response.

It may not do this perfectly, but not attempting to do at all it is a serious design failure.

Re: A three-page paper that shook philosophy, with lessons for software engineers

#99
“Justified true belief”? All our knowledge is subjective by definition. We don’t even know whether we’re living in a simulation.

Personally I doubt that we’re living in a simulation. But the fact that we could be, demonstrates that we don’t have objective knowledge. No cows needed in the field explain it

Philosophy might better be called “the history of flawed thinking”

Re: A three-page paper that shook philosophy, with lessons for software engineers

#100
post #77

I think it helps to look at the mind as a probabilistic survival engine than some truth engine. If there appears to be a cow in a random field the odds are extremely low that someone put a papier mache cow there. If there’s something that has 50 % chance of being a snake you panic and run because that’s a 50 % chance of dying. In the case of the authors bug yes the change he introduced had a good probability of being…

I think what you're saying is correct when it comes to perception with our senses, the kind of knowledge we share with the other higher animals. However, there is a higher level of knowledge that is unique to humans, which is rational in nature and can come up with certain knowledge. We can know certain mathematical and logical truths with certainty, such as 2 + 2 = 4 and that A and not A cannot both be true. We may…

I agree with your main points, but I think it's worth pointing out that even things like 2 + 2 = 4 and X + Y cows in fields A and B, all rest on certain definitions and sets of deductions, many of which go back down to basic axioms which have to be assumed (e.g. for arithmetic, see Peano axioms as an example: https://en.wikipedia.org/wiki/Peano_axioms).

- We have a definition of what a cow is, and we know that cows are discrete/physical objects, and have relatively fixed locations (i.e. that they are not like an electron cloud with a probabilistic location).

- We assume that fields A and B in your hypothetical have clear, non-overlapping boundaries.

- We assume that we are working in a fairly normal universe with a fairly standard model of physics, and that due to the way time works in this universe, a cow cannot simultaneously be located in both fields A and B.

- ...

- (this could get really pedantic and go on forever)

The point is, even the things "we can know with certainty", are only as certain as the framework of observations/deductions/axioms/etc. that they rest upon. Almost nothing is certain on its own, without any further layers of reasoning behind it.

Post reply on HN