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:

   27  cd
   28  mkdir session_e_practice
   29  ls
   30  rm -rf session_e_practice
   31  ls
   32  mkdir session_3_practice
   33  ls
   34  cd session_3_practice
   35  pwd
   36  touch budget.csv
   37  touch mentors.txt
   38  mkdir notes
   39  mkdir practice
   40  ls
   41  cd notes
   42  pwd
   43  ls
   44  touch git_notes.txt
   45  touch command_line_notes.txt
   46  cd ..
   47  pwd
   48  cd practice
   49  touch git_practice.txt
   50  mkdir projects
   51  cd projects
   52  touch game.js
   53  cd
   54  pwd
   55  ls
   56  cd session_3_practice
   57  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):

shane~$ mkdir git_homework
shane~$ cd git_homework
shane~/git_homework$ touch quotes.txt
shane~/git_homework$ ls
quotes.txt
shane~/git_homework$ git init
Initialized empty Git repository in /Users/shane/git_homework/.git/
shane~/git_homework$ git status
On branch master

No commits yet

Untracked files:
  (use "git add <file>..." to include in what will be committed)

	quotes.txt

nothing added to commit but untracked files present (use "git add" to track)
shane~/git_homework$ git add quotes.txt
shane~/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

shane~/git_homework$ git commit -m 'Initial commit.'
[master (root-commit) 8e4aeb3] Initial commit.
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
shane~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
shane~/git_homework[master]$ echo "My fake plants died because I did not pretend to water themn." >> quotes.txt
shane~/git_homework[master !]$ cat echo.txt
cat: echo.txt: No such file or directory
shane~/git_homework[master !]$ cat quotes.txt
My fake plants died because I did not pretend to water themn.
shane~/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")
shane~/git_homework[master !]$ git diff
diff --git a/quotes.txt b/quotes.txt
index e69de29..7ea2784 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+My fake plants died because I did not pretend to water themn.
shane~/git_homework[master !]$ git diff quotes.txt
diff --git a/quotes.txt b/quotes.txt
index e69de29..7ea2784 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+My fake plants died because I did not pretend to water themn.
shane~/git_homework[master !]$ git add quotes.txt
shane~/git_homework[master !]$ git status
On branch master
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	modified:   quotes.txt

shane~/git_homework[master !]$ git commit -m "Added quote."
[master b1ac9cd] Added quote.
 1 file changed, 1 insertion(+)
shane~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
shane~/git_homework[master]$ git log --pretty=oneline
b1ac9cdab02354e951f74fda7004ffb5340f71f3 (HEAD -> master) Added quote.
8e4aeb30099b2ab1a3a79a8fd1aa7567bf55d13f Initial commit.
shane~/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)
• thickness (float)

Methods:

• break_down
• stack
• close
• open
• fold

4. Questions/Comments/Confusions

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

1. More of a general question about github - Do I have to make each assignment public for the teachers to see it? That's what I've been doing so far, but I'm wondering if that's actually needed. Does that make my assignments visible to everyone else on Github as well?

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.