Stating and tracking assumptions have deep roots in philosophy and philosophy of science. How do you see yourself applying this concept in your work?

At the code level, there's general agreement that we should use inline comments, readme, and git to state/track our assumptions for that context. Shit breaks fast when we don't, so we're more on that perhaps.

But in the decision space where the analytics or modeling outcomes are applied to the business process or whatever, documenting assumptions happens at a project level. This is also at the level of the scientific method where the research question and hypotheses are stated (hopefully). …

assumptions concept datascience philosophy science tracking work