Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save aperezsantos/964779200a9e139bc8b70a1648e53cec to your computer and use it in GitHub Desktop.
Save aperezsantos/964779200a9e139bc8b70a1648e53cec to your computer and use it in GitHub Desktop.
Mod 0 Session 2 Practice Tasks

Session 2 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:

  359  pwd
  360  mkdir session_3_practice
  361  cd session_3_practice
  362  pwd
  363  mkdir notes
  364  mkdir practice
  365  cd practice
  366  pwd
  367  mkdir projects
  368  cd ..
  369  pwd
  370  touch budget.csv
  371  touch mentors.txt
  372  ls
  373  cd notes
  374  pwd
  375  touch git_notes.txt
  376  touch command_line_notes.txt
  377  ls
  378  cd ..
  379  cd practice
  380  touch git_practice.txt
  381  ls
  382  cd projects
  383  touch game.js
  384  ls
  385  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):

Last login: Tue Aug 20 12:57:10 on ttys000
Anas-MacBook-Pro:~ aperezsantos$ mkdir git_homework
Anas-MacBook-Pro:~ aperezsantos$ cd git_homework
Anas-MacBook-Pro:git_homework aperezsantos$ touch quotes.txt
Anas-MacBook-Pro:git_homework aperezsantos$ git init
Initialized empty Git repository in /Users/aperezsantos/git_homework/.git/
Anas-MacBook-Pro:git_homework aperezsantos$ 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)
Anas-MacBook-Pro:git_homework aperezsantos$ git add quotes.txt
Anas-MacBook-Pro:git_homework aperezsantos$ git status
On branch master

No commits yet

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

Anas-MacBook-Pro:git_homework aperezsantos$ git commit -m 'Initial commit'
[master (root-commit) e34ba22] Initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
Anas-MacBook-Pro:git_homework aperezsantos$ git status
On branch master
nothing to commit, working tree clean
Anas-MacBook-Pro:git_homework aperezsantos$ atom quotes.txt
Anas-MacBook-Pro:git_homework aperezsantos$ git status
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   quotes.txt

no changes added to commit (use "git add" and/or "git commit -a")
Anas-MacBook-Pro:git_homework aperezsantos$ git diff quotes.txt
diff --git a/quotes.txt b/quotes.txt
index e69de29..dd12856 100644
--- a/quotes.txt
+++ b/quotes.txt
@@ -0,0 +1 @@
+No hay que llorar, la vida es un carnaval, y las penas se van cantando. - La Vide es un Carnaval by Celia Crúz
Anas-MacBook-Pro:git_homework aperezsantos$ git add quotes.txt
Anas-MacBook-Pro:git_homework aperezsantos$ git commit -m 'First modified commit'
[master 1e7de7e] First modified commit
 1 file changed, 1 insertion(+)
Anas-MacBook-Pro:git_homework aperezsantos$ git status
On branch master
nothing to commit, working tree clean
Anas-MacBook-Pro:git_homework aperezsantos$ git log
commit 1e7de7e8867ac27782bd2b4f2d614f7bb65a53d7 (HEAD -> master)
Author: Ana Perez Santos <a.jperez@yahoo.com>
Date:   Tue Aug 20 13:25:32 2019 -0600

    First modified commit

commit e34ba22bc27f9751b59ec7e3ca5d7f19b68b5c9a
Author: Ana Perez Santos <a.jperez@yahoo.com>
Date:   Tue Aug 20 13:00:50 2019 -0600

    Initial commit

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)
  • length_ (integer)
  • height_ (integer)

Methods:

  • break_down
  • stack
  • open
  • flatten

4. Questions/Comments/Confusions

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

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