From f0f9bc4fc688339f52500dcd80aac3b57b619ef0 Mon Sep 17 00:00:00 2001 From: Jost Migenda Date: Tue, 25 Nov 2025 14:48:19 +0100 Subject: [PATCH 1/2] Update reflection exercise in coffee break Ensure reflection questions correspond to an episode before the break, after reordering --- episodes/15-coffee.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/episodes/15-coffee.md b/episodes/15-coffee.md index 2cb1ddc11..0f169c965 100644 --- a/episodes/15-coffee.md +++ b/episodes/15-coffee.md @@ -9,10 +9,5 @@ break: 15 Over break, reflect on and discuss the following: -- A common refrain in software engineering is "Don't Repeat Yourself". How do the techniques we've learned in the last - lessons help us avoid repeating ourselves? *Note that in practice there is some nuance to this and should be balanced - with doing the simplest thing that could possibly work.* -- What are the pros / cons of making a variable global or local to a function? -- When would you consider turning a block of code into a function definition? - - +- Think about data you are working with. Is it split up into multiple files? Would you be able to process these files using a for loop? +- If you are creating a new data set, how can file names you choose make it easier or harder to loop over the data files? From 3983ae6a1b2b64edd4ddb06e0f3136feb333cb36 Mon Sep 17 00:00:00 2001 From: Allen Lee Date: Fri, 13 Feb 2026 11:44:21 -0700 Subject: [PATCH 2/2] refine reflection exercises add some detail and suggested resources for file naming and data organization --- episodes/15-coffee.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/episodes/15-coffee.md b/episodes/15-coffee.md index 0f169c965..03646988a 100644 --- a/episodes/15-coffee.md +++ b/episodes/15-coffee.md @@ -9,5 +9,12 @@ break: 15 Over break, reflect on and discuss the following: -- Think about data you are working with. Is it split up into multiple files? Would you be able to process these files using a for loop? -- If you are creating a new data set, how can file names you choose make it easier or harder to loop over the data files? +- Think about existing data you are working with. Are the data split up into multiple files? How are the files named and organized? Would you be able to efficiently process these files using a for loop? +- If you are creating a new data set, what file naming and data organization practices would help you and your collaborators analyze and interpret your data now and in five or ten years? + +Here are some guides for file naming and data collection that we've found. Let us know if you have additional resources you'd like to share! + +- https://carpentries-lab.github.io/good-enough-practices/05-project_organization.html +- https://datamanagement.hms.harvard.edu/plan-design/file-naming-conventions +- https://guides.library.stanford.edu/data-best-practices +- https://book.the-turing-way.org/reproducible-research/rdm/rdm-storage/