Mod 0 Session 3 Practice Tasks

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:

56 mkdir session_3_practice 57 cd session_3_practice 58 touch budget.csv 59 touch mentors.txt 60 mkdir notes 61 cd notes 62 touch git_notes.txt 63 touch command_line_notes.txt 64 cd .. 65 mkdir practice 66 cd practice 67 touch git_practice.txt 68 mkdir projects 69 cd projects 70 touch game.fs 71 rm game.fs 72 touch game.js 73 ls 74 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):

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

No commits yet

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

new file:   quotes.txt

trishalanglois~/git_homework$ git commit -m 'Initial commit' [master (root-commit) 1f02fe7] Initial commit 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 quotes.txt trishalanglois~/git_homework[master]$ git status On branch master nothing to commit, working tree clean trishalanglois~/git_homework[master]$ echo "You can do hard things." >> quotes.txt trishalanglois~/git_homework[master !]$ git status On branch master Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory)

modified:   quotes.txt

no changes added to commit (use "git add" and/or "git commit -a") trishalanglois~/git_homework[master !]$ git diff diff --git a/quotes.txt b/quotes.txt index e69de29..054a887 100644 --- a/quotes.txt +++ b/quotes.txt @@ -0,0 +1 @@ +You can do hard things. trishalanglois~/git_homework[master !]$ git add quotes.txt trishalanglois~/git_homework[master !]$ git commit -m 'Hard things' [master 9e36d37] Hard things 1 file changed, 1 insertion(+) trishalanglois~/git_homework[master]$ git status On branch master nothing to commit, working tree clean trishalanglois~/git_homework[master]$ git oneline git: 'oneline' is not a git command. See 'git --help'. trishalanglois~/git_homework[master]$ git log --pretty=oneline 9e36d3777e082782da4f7261bcecbe8c04b114da (HEAD -> master) Hard things 1f02fe71cfd6a83c8f47286afef39119d17e029c Initial commit trishalanglois~/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)
• color (string)
• cost (float)

Methods:

• break_down
• stack
• hold
• fall

4. Questions/Comments/Confusions

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

1. I noticed that when I update my gist, I'm losing my line breaks in my blocks of code that I typed in my terminal. Any way to change this so it's easier for us to read when we go back to the regular, non-editing view?

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.

z_img_1.png

Hi Trisha - good job on these assignments. And yes, markdown provides some built in formatting that you can implement. Look into a numbered list, bulleted list, and/or using three back-ticks - this character: ` - to format what you've copy/pasted. Let me know if you have questions!