ogadaki
05/02/2020, 3:38 PMogadaki
05/02/2020, 3:43 PMIvan Reese
Edward de Jong / Beads Project
05/03/2020, 2:44 AMStefan
05/03/2020, 9:41 AMogadaki
05/03/2020, 2:43 PMogadaki
05/03/2020, 2:55 PMogadaki
05/03/2020, 3:02 PMDuncan Cragg
05/03/2020, 8:04 PMDuncan Cragg
05/03/2020, 8:06 PMogadaki
05/03/2020, 8:58 PMEdward de Jong / Beads Project
05/04/2020, 5:12 AMStefan
05/04/2020, 6:53 AMDuncan Cragg
05/04/2020, 1:01 PMogadaki
05/04/2020, 8:42 PMEdward de Jong / Beads Project
05/05/2020, 6:12 AMIvan Reese
Edward de Jong / Beads Project
05/05/2020, 8:20 PMIvan Reese
Duncan Cragg
05/06/2020, 8:01 AMStefan
05/06/2020, 10:22 AMEdward de Jong / Beads Project
05/06/2020, 5:31 PMogadaki
05/06/2020, 5:50 PMogadaki
05/06/2020, 6:00 PMI'd say the formulas are just as important. But when you expose too much, it becomes less accessible, and thus less useful as a teaching/learning tool. You don't need an encyclopedia entry to contain every possible detail in order for it to usefully convey critical info. So we need some other solution than just "make sure everyone is fully stats-literate and give them all the data and formulas". That doesn't scale.Yes, care must be taken to reveal only the level of information (here formulas) that is useful at the level reading. But maybe there is way to do it progressively? At least easier than the code for the Nicky Case article, where the formulas are in the JavaScript code mixed with UI parts. Maybe first the graph, then the parameters, then high level formulas, then lower level formulas, with as much level as needed down to the approximations the "last" formulas are doing and explicitly stating that they are abstractions and what this means in the reading of the whole story.
Konrad Hinsen
05/18/2020, 9:05 AMgman
06/15/2020, 3:44 AMDuncan Cragg
06/15/2020, 6:18 PMEdward de Jong / Beads Project
06/15/2020, 7:09 PM