---
# System prepended metadata

title: Check-in Day 1
tags: [sprint, ' NASA', ' TOPS']

---

---
tags: sprint, NASA, TOPS
---

# Check-in Day 1

**Tasks**
- Need to create learning profiles
- Need to create learning objectives

**Notes**
1. The learning objectives are intended to be used for the entire module -  not just one lesson
2. Expect learners to have minimal software experience
3. Expect learners to be already over-burdened and limited bandwidth to learn new techniques.

- Why share code? 
    - Community feedback, error checking, continuous review
    - Not rewriting something someone else has already done
- Learning objectives are designed to be module wide
- Ensure objectives are not too specific
    - we are teaching concepts, not technologies or specific skills
    - e.g. answer the question "Why should one care about …"
- General perspective: assume minimal programming background

Points on learning objectives we want to keep strongly:
- Taher: Understand cost/benefits
    - FAIR: findable, accessible, interoperable, reusable
    -  when you open source software there is a burden.
    -  why would one open source their code?
    -  Github is not allowed in some countries, how to get around?
        -  VPNs or alternative code hosting sites?
    - Code quality. What are some minimum requirements?
        - documentation
        - testing?
    - Contributor guidelines

- Ana: how can we be open and reproducible when some resources are insurmountable?
    - e.g. if I have access to a huge database and a HPC cluster, how I have an expectation that others can reproduce my analysis without these same resources?
    - Giving back to the OS software community
