Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save mcat56/e357dc335a5028e5ad387d342d0f4e1d to your computer and use it in GitHub Desktop.
Save mcat56/e357dc335a5028e5ad387d342d0f4e1d to your computer and use it in GitHub Desktop.
Mod 0 Session 3 Practice Tasks

Session 3 Practice Tasks

The assignments listed here should take you approximately 25 total minutes.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of the document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

1. Creating Files and Directories (10 min)

Need help? You can go back to the files/directories portion of the lesson here.

Scroll down to the bottom of this page and look at the image of the directories and files. Use commands in your terminal to create the directories and files structured exactly how they appear in the image.

When you're done, type history to see your commands. Copy and paste the commands that were used to create the directory and files:

163  ls
  164  mkdir session_3_practice
  165  ls
  166  cd session_3_practice
  167  touch budget.csv
  168  touch mentors.txt
  169  ls
  170  mkdir notes
  171  mkdir practice
  172  cd notes
  173  touch git_notes.txt
  174  touch command_line_notes.txt
  175  ls
  176  cd ..
  177  ls
  178  cd practice
  179  touch git_practice.txt
  180  mkdir projects
  181  cd projects
  182  touch game.js
  183  ls
  184  cd
  185  cd ..
  186  cd ..
  187  cd ..
  188  ls
  189  pwd
  190  ls
  191  cd ~
  192  ls
  193  cd session_3_practice
  194  ls
  195  history

Since this is just a practice directory, feel free to remove the parent directory session_3_practice when you're done with this exercise.

2. Git Practice (15 min)

You can reference the files/directories portion of the lesson here.

Follow the steps below to practice the git workflow. Be ready to copy-paste your terminal output as confirmation of your practice.

  1. Create a directory called git_homework. Inside of there, create a file called quotes.txt.
  2. Initialize the directory
  3. Check the git status
  4. Add your quotes.txt file to the staging area
  5. Check the git status
  6. Create an initial commit
  7. Check the status
  8. Add your favorite quote to the quotes.txt file
  9. Check the status
  10. Check the diff
  11. Add the changes to the staging area
  12. Commit the new changes
  13. Check the status
  14. Show the log in oneline (yes, oneline, not a spelling error) format

Copy and paste all of the terminal text from this process below (not just the history):

mcat56~/session_3_practice$ cd ..
mcat56~$ ls
Applications		Library			Public
Desktop			Movies			best_animals
Documents		Music			session_3_practice
Downloads		Pictures		sudo
mcat56~$ mkdir git_homework
mcat56~$ cd git_homework
mcat56~/git_homework$ touch quotes.txt
mcat56~/git_homework$ ls
quotes.txt
mcat56~/git_homework$ git init
Initialized empty Git repository in /Users/mcat56/git_homework/.git/
mcat56~/git_homework$ git add quotes.txt
mcat56~/git_homework$ git status
On branch master

No commits yet

Changes to be committed:
  (use "git rm --cached <file>..." to unstage)

	new file:   quotes.txt

mcat56~/git_homework$ git commit - "initial commit"
error: pathspec '-' did not match any file(s) known to git
error: pathspec 'initial commit' did not match any file(s) known to git
mcat56~/git_homework$ git commit -m "Initial commit."
[master (root-commit) b71cd49] Initial commit.
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
mcat56~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
mcat56~/git_homework[master]$ echo "Not all those who wander are lost." >> quotes.txt
mcat56~/git_homework[master !]$ git status
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   quotes.txt

no changes added to commit (use "git add" and/or "git commit -a")
mcat56~/git_homework[master !]$ git diff
diff --git a/quotes.txt b/quotes.txt
index e69de29..4af37bc 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+Not all those who wander are lost.
mcat56~/git_homework[master !]$ git add quotes.txt
mcat56~/git_homework[master !]$ git commit -m "Add quote."
[master 4a882d1] Add quote.
 1 file changed, 1 insertion(+)
mcat56~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
mcat56~/git_homework[master]$ git log --oneline
4a882d1 (HEAD -> master) Add quote.
b71cd49 Initial commit.
mcat56~/git_homework[master]$ 

IMPORTANT: Do not remove this git_homework directory. You will be using this directory during Thursday's session.

3. Classes, Attributes, and Methods

Look at the template below for a CardboardBox class. Fill in missing blanks with additional attributes and methods.

Class: CardboardBox

Attributes:

  • width (integer)
  • depth (integer)
  • height(integer)
  • color (string)

Methods:

  • break_down
  • stack
  • ship
  • add_label

4. Questions/Comments/Confusions

If you have any questions, comments, or confusions that you would an instructor to address, list them below:

  1. Sorry for late entry!

Extensions

  1. If time permits and you want extra git practice and alternative explanations (it's often beneficial to have something explained in many different ways), check out Codecademy's Git Course, particularly the first free item on the syllabus, "Basic Git Workflow". In Mod 0, we will not cover anything beyond Codecademy's intro section; however, you are welcome to check out the other git lessons listed on the syllabus if you want a head start.

  2. This course is how I personally learned command line. If time permits, I highly recommend reading and practicing.

  3. Also recommended by Jeff Casimir: Michael Hartl's Learn Enough Command Line.

  4. Add tab completion to make your life easier: Type Less. Do More.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment