Section 2 is estimated to take a total of 8-12 hours to complete. Similar to Section 1, this section of the project involves 📒reading, 👨🏽💻exercises, and 📝reflection questions. Make sure to manage your time well so that should you get stuck and need help, you have plenty of time to do so and meet the deadline.
- Vocabulary
- Get Set Up
- Part A: Growth Mindset
- Part B: Conditionals
- Vocabulary
- Reflections
- Commit Your Work in Git
- Push to GitHub
This section will introduce a number of new terms, that may feel a bit more complex. Write these terms in that special spot in your notebook now. Work to hold yourself accountable to updating definitions as you work through this section.
- if statements
- method
Using the Terminal, open the local copy of the repository that you created during setup. To do this, you will need to use the terminal command cd
to change into the directory that holds the repository. Once you are in the correct directory, use the terminal command atom .
to open the project repository. If you are having trouble with this, see the section1
instructions.
Read/watch one or both of the following:
- This 2-part blog post series discusses how having a growth mindset is helpful when learning to code, and how coding promotes a growth mindset!
- This video interview where an experienced Front-End engineer discusses learning about the concept of Growth Mindset and how that's changed how she sees her work and career. (The first 7 minutes are intros and a discussion on Developer Relations. After that, the conversation about Growth Midnset begins.)
Then, consider on the following questions. We will ask you to share some of these responses at the end of this section.
- What are two points from the article or video that either resonated with you, or were brand new to you?
- In which ways do you currently demonstrate a Growth Mindset? In which ways do you not?
- What is something you are good at or knowledgeable at now, that you once weren't? How did you get those skills/knowledge? Was it hard at some point?
One of the most important concepts in computer programming is knowing when and how to tell the computer to do either one thing or another thing based on a set of simple criteria. We accomplish this with If-Statements and Conditionals, which you will learn about today.
When you are all done with the lessons, exercises, and questions for today, you will once again use git to save your work locally, and then send your work to GitHub.
-
Work through the following lessons. Any files that you create while working can be kept in today's
exercises
directory.-
What If? from Learn Ruby the Hard Way.
-
Else and If from Learn Ruby the Hard Way.
-
Making Decisions from Learn Ruby the Hard Way.
-
Conditionals from Ruby in 100 Minutes.
-
-
Work through the
if_statements.rb
file in thesection2/exercises
directory.
Look back at that special spot in your notebook for vocabulary. Hopefully you updated it with definitions, diagrams, and code samples as you went through this section. If not, do so now. This will be part of this sections deliverables.
📝 Answer the prompts in the reflection.md
file in the section2
directory. If you need a reminder on how to format your markdown, this is the Markdown Cheatsheet!
When you are finished with all of the section2
activities, use the Terminal to run the following commands in order to save your work to your local Git repository.
git add section2/exercises
git add section2/reflection.md
git status
- you should see only green filenames - if you see any that are red, continue togit add
those files untilgit status
shows all green files.git commit -m "Add Section 2 work"
You've saved your work to Git on your local machine, but your repository on GitHub doesn't reflect it yet. You update the remote GitHub repository with your new local commits when you push
your changes.
Run:
git push origin main
You should now be able to log in to GitHub, navigate to your remote repository and see all the work you did in this section!