- Description
- Learning Outcomes
- Assignments
- Contacts
- Delivery of the Learning Module
- Schedule
- Requirements
- Resources
- Folder Structure
This module introduces the Unix shell language and covers file and directory navigation and manipulation. Participants gain proficiency in various commands, script creation, and writing basic functions using pipes, filters, and loops.
Participants will acquire problem-solving skills through live coding sessions. Additionally, they will explore the concept of reproducibility and its integration into their work.
By the end of the module, participants will be able to:
- Comfortably access and navigate the terminal
- Create, modify and delete directories and files
This module has two types of activities.
- Assignments are mandatory, and form part of your evaluation.
- Homework is not assessed, but are provided to you for extra practice. We encourage you to check each other's homework solutions during Work Periods or ask a Learning Support!
Participants should review the Assignment Submission Guide for instructions on how to complete assignments in this module.
Assignments are typically due on the Sunday following the module's live learning session.
Questions can be submitted to the #cohort-4-help channel on Slack
-
Technical Facilitator:
- Simeon Wong [email protected]
-
Learning Support Staff:
- Anjali Shrivastava [email protected]
- Moniz Chan [email protected]
- Pedram Asli [email protected]
This module will include live learning sessions and optional, asynchronous work periods. During live learning sessions, the Technical Facilitator will introduce and explain key concepts and demonstrate core skills. Learning is facilitated during this time. Before and after each live learning session, the instructional team will be available for questions related to the core concepts of the module. Optional work periods are to be used to seek help from peers, the Learning Support team, and to work through the homework and assignments in the learning module, with access to live help. Content is not facilitated, but rather this time should be driven by participants. We encourage participants to come to these work periods with questions and problems to work through. Participants are encouraged to engage actively during the learning module. They key to developing the core skills in each learning module is through practice. The more participants engage in coding along with the instructional team, and applying the skills in each module, the more likely it is that these skills will solidify.
| Day 1 | Day 2 | Day 3 | Day 4 | Day 5 | |
|---|---|---|---|---|---|
| Week 1 | Live Learning Session 1 (Shell) | Live Learning Session 2 (Shell) | Live Learning Session 3 (Git & GitHub) | Work Period 1 | Work Period 2 |
- Participants are not expected to have any coding experience; the learning content has been designed for beginners.
- Participants are encouraged to ask questions, and collaborate with others to enhance their learning experience.
- Participants must have a computer and an internet connection to participate in online activities.
- Participants must not use generative AI such as ChatGPT to generate code in order to complete assignments. It should be used as a supportive tool to seek out answers to questions you may have.
- We expect participants to have completed the steps in the onboarding repo.
- We encourage participants to default to having their camera on at all times, and turning the camera off only as needed. This will greatly enhance the learning experience for all participants and provides real-time feedback for the instructional team.
Feel free to use the following as resources:
- Copy and paste your error message
- Copy and paste the code that caused the error, and the last few commands leading up to the error
- Write down what you are trying to accomplish with your code. Include both the specific action, and the bigger picture and context
- (optional) Take a screenshot of your entire workspace
- Sometimes, the error has common solutions that can be easy to find!
- This will be faster than waiting for an answer
- If none of the solutions apply, consider asking a Generative AI tool
- Paste your code, the error message, and a description of your overall goals
- Since we're all working through the same material, there's a good chance one of your peers has encountered the same error, or has already solved it
- Try searching in the DSI Certificates Slack help channel for whether a similar query has been posted
- If the question has not yet been answered, post your question!
- Describe your the overall goals, the context, and the specific details of what you were trying to accomplish
- Make sure to copy and paste your code, your error message
- Copying and pasting helps:
- your peers and teaching team quickly try out your code
- others to find your question in the future
- Asking for Help - The Odin Project
- How do I ask a good question? - Stack Overflow
- The XY problem: A question pitfall that won't get useful answers
- How to create a minimal reproducible example
Below is an outline of the folder structure for this module:
.
├── .github
├── 01_materials
├── 02_activities
├── 03_instructional_team
├── 04_this_cohort
├── .gitignore
├── LICENSE
├── README.md
└── steps_to_ask_for_help.png
- .github: Contains issue templates and pull request templates for the repository.
- materials: Module slides and interactive notebooks (.ipynb files) used during learning sessions.
- activities: Contains graded assignments, exercises, and homework to practice concepts covered in the learning module.
- instructional_team: Resources for the instructional team.
- this_cohort: Additional materials for this cohort.
- .gitignore: Files to exclude from this folder, specified by the Technical Facilitator
- LICENSE: The license for this repository.
- README: This file.
- steps_to_ask_for_help.png: Guide on how to ask for help.