6 ms·
> Computers have been invented to surprise us... If we knew what computers do, we would not use them, and we would not have built any. This is just trying to s
by magicalhippo 6y ago
> Computers have been invented to surprise us... If we knew what computers do, we would not use them, and we would not have built any.
This is just trying to sound clever for the sake of sounding clever. The first bit is factually wrong in any non-trivial way, and the counter argument for the second bit is the very next slide.
- K0balt 6y ago... If the answer to the square root of 91287346540 is unsurprising, you should just be able to say precisely what it is without working it out. I think the issue is the definition of surprise is the issue here. It may be unsurprising to receive a birthday gift, but the exact gift is still a surprise.
- magicalhippo 6y agoThe answer to the square root of 91287346540 is trivially surprising. It is not surprising in any interesting way.
- Joker_vD 6y ago...what is the least trivially surprising natural number? That is, would such a number still be trivially surprising?
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- magicalhippo 6y ago> what is the least trivially surprising natural number? Whatever it is, if it exists, it's not what computers were invented to find.
- ukj 6y agoRed herring. Trivial and non-trivial surprises are still surprising.
- vsareto 6y agoPredicating this on surprise is the problem. We still would have used computers for data entry, storage, and transmission even though we know humans could do that because they're simply superior than paper and typewriters in most ways. There's nothing surprising about that.
- deleted 6y ago[deleted]
- ukj 6y agoThis seems like an unnecessary ad hominem. Just because something is factually incorrect doesn’t mean it isn’t true. Surprise is a measure of new Information (ref: Shannon). It is simply a tautology. To be unsurprised is to provide the answer before the computer produces it.
- magicalhippo 6y ago> This seems like an unnecessary ad hominem. I didn't mean it as such. I just found it wrong, and thus not very interesting, for the reasons I stated. > Surprise is a measure of new Information (ref: Shannon). Ah. Not read Shannon himself, so wasn't aware he used his own special definition of surprise. All the work I've seen has talked about information or entropy. > To be unsurprised is to provide the answer before the computer produces it. I'm still not buying that definition of surprise...
- _jal 6y ago> so wasn't aware he used his own special definition of surprise. All the work I've seen has talked about information or entropy. It isn't 'special', and directly relates to the definition of entropy.
- magicalhippo 6y agoWell guess I've either read sources which avoided that word when defining entropy, or I mentally erased it because of the poor fit.
- ukj 6y ago"Poor fit" is an ironic choice of words. https://en.wikipedia.org/wiki/Goodness_of_fit https://en.wikipedia.org/wiki/Goodness_of_fit Fundamentally statistics is Information theory. https://en.wikipedia.org/wiki/Principle_of_maximum_entropy#History https://en.wikipedia.org/wiki/Principle_of_maximum_entropy#H...
- ukj 6y ago
- pron 6y agoAs a formal methods researcher, he expresses in a clever way what formal method researchers know: it is extremely hard to establish interesting non-trivial properties of programs. His cleverness is pointing out that this is intentional: if we could easily tell all interesting properties of the results our programs give us, we wouldn't need them in the first place (of course this isn't always true, but don't be so literal). It's another way of saying that software exists for its essential complexity, and that that complexity -- as formal methods/software analysis research tells us -- is high.
- hinkley 6y ago> if we could easily tell all interesting properties of the results our programs give us, we wouldn't need them in the first place At least to a degree, that may be our own hubris instead of an essential quality of programming. Rarely do I encounter a program whose problems are in their essential complexity. What I see instead is people convincing themselves that all of their pain is necessary. We have a lot of architectural astronauts who seek complexity for its own sake. We have feature factories adding new complexity all the time. Code being written to justify code still being written - programming bureaucracies. Like moths to a flame we reach for complexity. And we reach, and we reach, and we reach. I have spent a lot of my career working to scale developers vertically. In software, when communication is the bottleneck, we either fix it and keep scaling horizontally, or can’t and work to scale our hardware vertically. Achievements in developer communications have been rare, and yet we keep young to scale horizontally like we don’t already know how this story ends. Dusty, old, 25th anniversary editions of Brooks’ lie unheaded on the shelf. Boringly predictable code is how I do that. Tools that automate very repetitive but error prone processes are part of that mix. In which case I definitely know the answer, I just really want to make sure I get it. This is, after all, how software got started in the first place. The logical conclusion of a story started by Monsieur Jacquard. Some people get really uncomfortable in the face of such changes, but they are typically folks I have already identified as part of the complexity problem. Some can be converted, others cannot. We are poisoning the well and standing around complaining about it.
- pron 6y ago