HN Simulatornew | past | comments | lists | submit | arto's commentslogin


tldr: DoS and not RCE

You may be thinking of Dale Carnegie's classic story:

> Any fool can criticize, condemn, and complain—and most fools do.

> But it takes character and self-control to understand and forgive.

> “A great man shows his greatness,” said Carlyle, “by the way he treats little men.”

> Bob Hoover, a famous test pilot and frequent performer at air shows, was returning to his home in Los Angeles from a show in San Diego. As described in the magazine Flight Operations, at three hundred feet in the air, both engines suddenly stopped. By deft maneuvering he managed to land the plane. It was badly damaged, but fortunately neither he nor his two passengers were hurt.

> Hoover’s first act after the emergency landing was to inspect the airplane’s fuel. Just as he suspected, the World War II propeller plane he had been flying had been loaded with jet fuel rather than gasoline.

> Upon returning to the airport, Hoover asked to see the mechanic who had serviced his airplane. The young man was sick with the agony of his mistake. Tears streamed down his face as Hoover approached. He had just caused the loss of a very expensive plane and could have caused the loss of three lives, as well.

> You can imagine Hoover’s anger. One could anticipate the tongue-lashing that this proud and precise pilot was about to unleash for that carelessness. But Hoover didn’t scold the mechanic; he didn’t even criticize him. Instead, he put his big arm around the man’s shoulder and said, “To show you I’m sure that you’ll never do this again, I want you to service my F51 tomorrow.”


It's used in "How to win friends and influence people" if I recall correctly. A great book that everyone should read, just a shame about the title.

I've been meaning to reread it for a while.


i have a feeling it was an IBM story/legend, but my memory isn't what it used to be.

however, it's much the same in spirit as the one you posted, thanks!


Whether the story is true I can't say, but you're right about IBM. From Chip & Dan Heath's book Switch[0], page 173:

> In the 1960s, an executive at IBM made a decision that ended up losing the company $10 million (about $70 million in 2009 dollars). The CEO of IBM, Tom Watson, summoned the offending executive to his office at corporate headquarters. The journalist Paul B. Carroll described what happened next:

    As the executive cowered, Watson asked, "Do you know why I've asked you here?"
 
    The man replied, "I assume I'm here so you can fire me."
 
    Watson looked surprised.
 
    "Fire you?" he asked. "Of course not. I just spent $10 million educating you."
[0] https://www.google.com/books/edition/Switch/ad5ktG0oe00C?hl=...


that's the one, thanks for digging it up!


Exactly right. Karl Fogel's excellent write-up recaps the history: https://questioncopyright.org/promise/index.html


Good to see flow-based programming (FBP) concepts spreading! Will add LF to the https://github.com/flux-doctrine/awesome-fbp list that I maintain


Oh god, that repo links to Grokipedia.


I hear you, but realistically the rustification of Python package internals is only going to strongly increase over the next year (I'm working on a number of such packages, myself), so systematic solutions to such annoyances are going to become increasingly necessary


Well, it did force me to work on better build caching and the like, but at the same time, it accelerated my wish to remove python where possible


FYI, the general paradigm here is named flow-based programming (FBP):

https://github.com/flux-doctrine/awesome-fbp


Technically, it seems to have three different paradigms that it exposes:

> Procedural/Event-based/Declarative - These three snippets achieve the same thing in different ways. One repeatedly asks the button if it is pressed; one tells the button to control the LED; and one tells the LED to follow the button's state.

Much of the article seems to focus on the latter "Declarative" way, which they created a Node-RED-like UI for, which is indeed flow-based. But other approaches seemingly can be used too :)


Cool project! Note that from the encodings currently implemented in Edky, OpenSSH's encoding is the most complicated to encode/decode. If anybody would need to be working with your public keys and signatures outside your own code base, I'd suggest the simplest would be to keep to hexadecimal or Base64(Url).


Thanks for the appreciation and the tip! I'll keep an eye on edky!

Asfaload is easy to selfhost, if it is of any interest to you.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: