Knowable unknown: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
{{a|devil|{{subtable|{{unknowns}}}}}}{{d|Knowable unknown|/ˈnəʊəbᵊl ʌnˈnəʊn/ (also “constructive known”) |n|}}Something you don’t know, and can’t know, but you believe you can as good as know as long as you have enough data and clever enough [[algorithm]]s.
{{a|devil|{{subtable|{{unknowns}}}}}}{{d|Knowable unknown|/ˈnəʊəbᵊl ʌnˈnəʊn/ (also “constructive known”) |n|}}Hailing not from Donald Rumsfeld’s famous taxonomy, but the JC’s private one, a [[knowable unknown]] is something you don’t know, and can’t know, but believe you can ''as good as know'', just as long as you have enough data and clever enough [[algorithm]]s and suitable reality distortion fields and bullshit detector defeat devices installed around you.


Such as that options will behave according to the [[Black-Scholes option pricing model]].
Such as that “options will behave as predicted by the [[Black-Scholes option pricing model]].


the problem with knowable unknowns is that they are irritatingly time-bound, and tend to be knowable at all the times where you don’t really need to know them, but then become suddenly impenetrably unknowable just when your pants are down.  
The problem with [[knowable unknowns]] is that they are irritatingly time-bound, and tend to be knowable at all the times where you don’t really need to know them, but then become suddenly impenetrably unknowable just when your pants are down.  
 
Victims of expiring [[knowable unknowns]] include [[Long-Term Capital Management]] in 1998, the entire [[financial services]] industry in 2008,


This is not from Donald Rumsfeld’s taxonomy, but the JC’s.
{{sa}}
{{sa}}
*[[System redundancy]]
*[[System redundancy]]
*[[Unknowns]]
*[[Unknowns]]