Live data from Hacker News

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

jsomers.net

11–20 of 185 posts

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

#11
post #4

This hits close to me as a possible reason why I could never get good at solving geometry problems, solid geometry especially. Most problems would be trivial when one assumes specific preconditions, but my mind was always wandering around, looking at all potential sides of a problem and I could never solve anything. To quote the author from my particular pov: a problem has multiple potential causes, and you have ever…

This is surprising.

Russian geometry problems, as I remember them, required creative thinking, which seem to be exactly the opposite to what you are describing.

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

#13

These cases seem to come up often (weekly?) in software development. I wonder how often they come up in other professions. One common case is when you change or delete a comment, and suddenly something breaks. It couldn't have been the comment... but it was working fine before my edit... wasn't it?

I have had bugs that where fixed by recompiling the entire application

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

#15
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 the cause. However he could have increased the probability by going back over commits and confirming that his exact commit introduced the bug. Now the probability goes even higher. But it could still be machine specific a cosmic ray or whatever but the odds are over whelmingly low.

In practice causal reasoning also works in a probabilistic fashion.

I have a simple model saying that if a planes engine is on then it’s flying. Its a single step probability and so it’s not very accurate in the real world.

I do a bunch of experiments and say a plane is flying if the engine is on and air is going over it’s wings faster than a certain speed.

Now we have two correlations connected by a causal model that works in many other cases. Hence the probability of it being correct rises.

But at the same time we should never mistake direct correlation for causality. But in daily life it’s “good enough”.

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

#17

These cases seem to come up often (weekly?) in software development. I wonder how often they come up in other professions. One common case is when you change or delete a comment, and suddenly something breaks. It couldn't have been the comment... but it was working fine before my edit... wasn't it?

Or the bugs that disappear when you're debugging and then come back hen you're not.

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

#18

The propensity for mistaking belief for facts certainly take daily hits as a software developer. "How come this simple thing isn't working? I thought of everything didn't I?". After a while you are forced to realize that belief isn't the same as reality. It seems insights like this don't easily translate into other domains though, like relationships, dearly held political views etc. We prefer to think of them as base…

Hard to translate to other domains without a tool to prove you wrong until you are right.

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

#19

These cases seem to come up often (weekly?) in software development. I wonder how often they come up in other professions. One common case is when you change or delete a comment, and suddenly something breaks. It couldn't have been the comment... but it was working fine before my edit... wasn't it?

And then as you look closer, you wonder how it ever worked. Hang on, did it ever work?

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

#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.
Post reply on HN