Learning Objectives
- Repositories
- Commits
- History
- GitHub
Lesson Materials
If you are using Odin as your primary learning materials, please go to each link in this list and read through the content on that page. If there are links you are redirected to as you read/work through the content, follow those links as well and read the content there also.
- The Odin Project – Text Editors
- The Odin Project – Command Line Basics
- The Odin Project – Setting Up Git
- The Odin Project – Introduction to Git
- The Odin Project – Git Basics
If you are using Treehouse as your primary learning materials, please go through the following courses in treehouse:
- Introduction to git Course (186 minutes)
Assignments
Coding Assignment
For sections 2-6, students will be working on this “Personal Portfolio” project and all the code will be located in the same GitHub repository — each week you will just add more to it. The Main Repository link for your class is the entire project overview and contains the instructions for this week (Lesson 2.1) and all the others. Lesson 2.1 explains how to get your repository setup.
Mindset Assignment
By this stage in the course, you’ve probably run into a bug or two that has taken some time—maybe much longer than your anticipated!—to figure out, or perhaps one that required showing your code to a mentor to get unstuck. If you did work with a mentor to figure out that bug, you likely observed them put a few debugging practices into action. Debugging is the process of working through technical challenges when something is broken or not working as expected, and it is a HUGE part of most developer’s day-to-day. Ideally, we would write beautiful, perfect code the first time around and introduce no bugs… but we’re human after all, so that’s not the reality.
Given, we humans do (often) introduce bugs into our programs, it’s important to invest time into strengthening your debugging processes—coming up with hypotheses, observing and investigating how things are working, and piecing together the clues to figure out what’s going on. Only then can you know how to fix it!
This week, reflect on the following…
– When asked to think about debugging, what are the first 3 adjectives that jump to mind?
– Are there any debugging practices that you’ve already tried and found helpful?
– Any you haven’t tried yet, but want to practice in this upcoming week?
When you’ve completed your Coding Assignment, and have read and thought about the mindset questions above, submit ALL of your assignments (link to your pull request on GitHub and mindset) using the Homework Assignment Submission Form.
Other Materials
This video was shared in last week’s lesson. If you have not viewed the video, please take a look this week. The video gives you an overview of Visual Studio Code, a software program that allows you to write your code, arrange your file structures, and even has helpful built-in features and optional extensions to make code writing a simpler process.
NOTE: If you already have a preferred code editor that you are using and you don’t want to change, you can disregard this information. We do not require students to use Visual Studio Code, but it is a helpful and common tool in the industry and we wanted to share this information with you. Here is the link to the page where you can download: Visual Studio Code
Link to open the video in a new window