sertmer/mod_0_session_3_practice_tasks.md

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:

23  pwd
   24  mkdir session_3_practice
   25  pwd
   26  cd session_3_practice/
   27  ls
   28  touch budget.csv
   29  touch mentors.txt
   30  mkdir notes
   31  ls
   32  cd notes
   33  touch git_notes.txt
   34  touch command_line_notes.txt
   35  ls
   36  cd ..
   37  mkdir practice
   38  cd practice
   39  touch git_practice.txt
   40  mkdir projects
   41  cd projects/
   42  touch game.js
   43  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.

Create a directory called git_homework. Inside of there, create a file called quotes.txt.
Initialize the directory
Check the git status
Add your quotes.txt file to the staging area
Check the git status
Create an initial commit
Check the status
Add your favorite quote to the quotes.txt file
Check the status
Check the diff
Add the changes to the staging area
Commit the new changes
Check the status
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):

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

No commits yet

nothing to commit (create/copy files and use "git add" to track)
scottertmer~/git_homework$ ls -a
.	..	.git
scottertmer~/git_homework$ git commit 'Initial commit'
error: pathspec 'Initial commit' did not match any file(s) known to git
scottertmer~/git_homework$ git add quotes.txt
fatal: pathspec 'quotes.txt' did not match any files
scottertmer~/git_homework$ ls
scottertmer~/git_homework$ touch quotes.txt
scottertmer~/git_homework$ ls
quotes.txt
scottertmer~/git_homework$ git add quotes.txt 
scottertmer~/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

scottertmer~/git_homework$ git commit -m 'Initial commit'
[master (root-commit) 36b4cec] Initial commit
 Committer: Alan Turing <[email protected]>
Your name and email address were configured automatically based
on your username and hostname. Please check that they are accurate.
You can suppress this message by setting them explicitly:

    git config --global user.name "Your Name"
    git config --global user.email [email protected]

After doing this, you may fix the identity used for this commit with:

    git commit --amend --reset-author

 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
scottertmer~/git_homework[master]$ git config --global user.name "sertmer"
scottertmer~/git_homework[master]$ git config --global user.email [email protected]
scottertmer~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
scottertmer~/git_homework[master]$ echo "We are what we pretend to be, so we must be careful about what we pretend to be." >>
-bash: syntax error near unexpected token `newline'
scottertmer~/git_homework[master]$ echo "We are what we pretend to be, so we must be careful about what we pretend to be. >> quotes.txt
> cat quotes.txt
> 
scottertmer~/git_homework[master]$ cat quotes.txt
scottertmer~/git_homework[master]$ ls
quotes.txt
scottertmer~/git_homework[master]$ echo "We are what we pretend to be, so we must be careful about what we pretend to be." >> quotes.txt 
scottertmer~/git_homework[master !]$ git.status
-bash: git.status: command not found
scottertmer~/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")
scottertmer~/git_homework[master !]$ git add quotes.txt 
scottertmer~/git_homework[master !]$ git diff
scottertmer~/git_homework[master !]$ git digg quotes.txt 
git: 'digg' is not a git command. See 'git --help'.

The most similar command is
	diff
scottertmer~/git_homework[master !]$ git diff quotes.txt 
scottertmer~/git_homework[master !]$ cat quotes.txt 
We are what we pretend to be, so we must be careful about what we pretend to be.
scottertmer~/git_homework[master !]$ git commit -m 'added quote'
[master 99d6f1e] added quote
 1 file changed, 1 insertion(+)
scottertmer~/git_homework[master]$ git status
On branch master
nothing to commit, working tree clean
scottertmer~/git_homework[master]$ oneline
-bash: oneline: command not found
scottertmer~/git_homework[master]$ git log --pretty=oneline
99d6f1ebe7563ca3b784a2577722bfd19de27683 (HEAD -> master) added quote
36b4ceceae08d4992a3a3e166f09bb0f2492d63e Initial commit
scottertmer~/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)
Length (integer)
color (string)

Methods:

break_down
stack
fold
close

4. Questions/Comments/Confusions

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

I really wasnt sure about showing the log in oneline format, so I hope I got that right. I also noticed my terminal asking me for my name and email at one point, along with instructions on how to enter it... I did that, but what is the use of that? when would that come into play? Thanks!

Extensions

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.
This course is how I personally learned command line. If time permits, I highly recommend reading and practicing.
Also recommended by Jeff Casimir: Michael Hartl's Learn Enough Command Line.
Add tab completion to make your life easier: Type Less. Do More.