A friend turned me on to asking Fable to wireframe different options when I have a tricky UI problem with a lot of requirements and too many possible paths. Game changing. Gives me flashbacks to what @bmoesta taught me about using orthogonal arrays when an engineering problem has too many variables. It's not about one-shotting the answer. It's about getting enough contrast between options to clarify which variables (aka "factors") are most important. Not which solution is best -- which variables matter more. THEN I can use that knowledge to decide to fix certain variables and narrow the space…
This book manages to pull all of that together in a way that's genuinely readable and engaging, helped along by anecdotes from his own policymaking experience that both clarify the arguments and make them feel concrete and accessible to a much broader audience.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.