Readit NewsSo they set out to describe it as „an accident“ because „blameless post-mortems“ are something people really like?
Also this article falls into the trap of trying to sound smart by using, sorry, „by effecting the usage of“ big fancy words. I’ve read Supreme Court transcripts and judgements, and I can understand them. This is overtaxing my buzzword ingestion.
As someone who has operated bug bounty programs, understanding what processes might have prevented things from going off the rails _in spite of_ internal actors with different motivations is very helpful to me. Placing all of the blame on an individual removes the opportunity to improve things.
Thanks for building this!
edit: For what it's worth, the use case and value of something like this was immediately apparent to me.
This made me chuckle, because I am at this very moment trying to apply the "tagless final style" described here[0] to a custom GUI in a personal-for-fun-and-learning ocaml project : )
[0] https://okmij.org/ftp/tagless-final/course/optimizations.htm...
However, as I started off with, I’m always willing to try something out or see the reason in something. Can anyone give me a practical applied way in which category theory is a benefit to your design rather than just creating higher level jargon to label your current design with?
And yes, in finance, the correlations between asset classes shoot up toward 1 in periods of crisis (black swan event) . Hence, the research for tail-hedging strategies...
Related to what you said here, I was surprised there wasn't a comparison with Vine Copulas in the paper or thread! But this is pretty far outside of my realm of expertise, so maybe it shouldn't be surprising.