Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Apprendre Documenting Assumptions and Decisions | Documentation for Data Science Projects
Practice
Projects
Quizzes & Challenges
Quizzes
Challenges
/
Productivity Tools for Data Scientists

bookDocumenting Assumptions and Decisions

When you work on data science projects, documenting your assumptions, data sources, and key decisions is essential for building analyses that others — and your future self — can understand and trust. As you explore data, select features, or choose modeling techniques, you make choices based on context, constraints, and available information. Without recording the why behind these choices, your reasoning can become lost, making it difficult to justify or reproduce your work later. Clear documentation helps others follow your thought process, enables seamless project handoffs, and provides transparency for stakeholders who may question the basis of your conclusions. You should always aim to capture not just what you did, but why you did it.

Note
Note

Make it a practice to use markdown cells in your notebooks to record the rationale for major steps. For example, after cleaning data or choosing a model, add a short explanation of your reasoning, referencing the importance of documenting assumptions, sources, and decisions as described above.

Notebook with well-documented assumptions
expand arrow
  • Contains markdown cells explaining data source choices, such as why a particular dataset was selected and what limitations it has;
  • Clearly states assumptions, like Assume missing values are random, with justification;
  • Describes why certain preprocessing steps or models were chosen, referencing project goals or constraints;
  • Future readers can quickly understand the context and reasoning behind every major action.
Notebook without documented assumptions
expand arrow
  • Lacks explanations for data source selection or preprocessing steps;
  • No record of why missing values were handled a certain way or why a specific model was used;
  • Future readers are left guessing about the rationale, making it hard to validate, critique, or extend the analysis.
question mark

Which statement best reflects a recommended practice for documenting data science projects?

Select the correct answer

Tout était clair ?

Comment pouvons-nous l'améliorer ?

Merci pour vos commentaires !

Section 3. Chapitre 1

Demandez à l'IA

expand

Demandez à l'IA

ChatGPT

Posez n'importe quelle question ou essayez l'une des questions suggérées pour commencer notre discussion

bookDocumenting Assumptions and Decisions

Glissez pour afficher le menu

When you work on data science projects, documenting your assumptions, data sources, and key decisions is essential for building analyses that others — and your future self — can understand and trust. As you explore data, select features, or choose modeling techniques, you make choices based on context, constraints, and available information. Without recording the why behind these choices, your reasoning can become lost, making it difficult to justify or reproduce your work later. Clear documentation helps others follow your thought process, enables seamless project handoffs, and provides transparency for stakeholders who may question the basis of your conclusions. You should always aim to capture not just what you did, but why you did it.

Note
Note

Make it a practice to use markdown cells in your notebooks to record the rationale for major steps. For example, after cleaning data or choosing a model, add a short explanation of your reasoning, referencing the importance of documenting assumptions, sources, and decisions as described above.

Notebook with well-documented assumptions
expand arrow
  • Contains markdown cells explaining data source choices, such as why a particular dataset was selected and what limitations it has;
  • Clearly states assumptions, like Assume missing values are random, with justification;
  • Describes why certain preprocessing steps or models were chosen, referencing project goals or constraints;
  • Future readers can quickly understand the context and reasoning behind every major action.
Notebook without documented assumptions
expand arrow
  • Lacks explanations for data source selection or preprocessing steps;
  • No record of why missing values were handled a certain way or why a specific model was used;
  • Future readers are left guessing about the rationale, making it hard to validate, critique, or extend the analysis.
question mark

Which statement best reflects a recommended practice for documenting data science projects?

Select the correct answer

Tout était clair ?

Comment pouvons-nous l'améliorer ?

Merci pour vos commentaires !

Section 3. Chapitre 1
some-alt