Skip to content

Instantly share code, notes, and snippets.

@vladd-png

vladd-png/mod_0_session_2_practice_tasks.md

Forked from damwhit/mod_0_session_2_practice_tasks.md
Last active August 22, 2019 07:06
Show Gist options
  • Save vladd-png/9923705e3cd72f4714b2d618f2ebb99d to your computer and use it in GitHub Desktop.
Save vladd-png/9923705e3cd72f4714b2d618f2ebb99d to your computer and use it in GitHub Desktop.
Download ZIP
Mod 0 Session 2 Practice Tasks
Raw
mod_0_session_2_practice_tasks.md

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:

229  cd virginialadd
  230  ls
  231  mkdir session_3_practice
  232  cd session_3_practice
  233  touch budget.csv
  234  touch mentors.txt
  235  ls
  236  mkdir notes
  237  mkdir practice
  238  cd notes
  239  touch git_notes.txt
  240  touch command_line_notes.txt
  241  ls
  242  cd session_3_practice
  243  cd ..
  244  ls
  245  cd practice
  246  touch git_practice.txt
  247  mkdir projects
  248  cd projects
  249  touch game.js
  250  history
virginialadd~/session_3_practice/practice/projects$

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: Sun Aug 18 22:16:50 on ttys000 virginialadd~$ ls Applications Library Pictures Desktop Movies Public Documents Music bucketstationlocations Downloads Notes virginialadd~$ mkdir git_homework virginialadd~$ cd git_homework virginialadd~/git_homework$ touch quotes.txt virginialadd~/git_homework$ git init Initialized empty Git repository in /Users/virginialadd/git_homework/.git/ virginialadd~/git_homework$ ls quotes.txt virginialadd~/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) virginialadd~/git_homework$ add quotes.txt -bash: add: command not found virginialadd~/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) virginialadd~/git_homework$ git add quotes.txt virginialadd~/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 virginialadd~/git_homework$ git commit -m 'Initial commit' [master (root-commit) df24458] Initial commit 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 quotes.txt virginialadd~/git_homework[master]$ git status On branch master nothing to commit, working tree clean virginialadd~/git_homework[master]$ echo 'Sunshine everyday makes a desert.' >> quotes.txt virginialadd~/git_homework[master !]$ echo 'Speak of the devil, and the devil shall appear.' >> quotes.txt virginialadd~/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") virginialadd~/git_homework[master !]$ git diff quotes.txt diff --git a/quotes.txt b/quotes.txt index e69de29..5af1b42 100644 --- a/quotes.txt +++ b/quotes.txt @@ -0,0 +1,2 @@ +Sunshine everyday makes a desert. +Speak of the devil, and the devil shall appear. virginialadd~/git_homework[master !]$ git add quotes.txt virginialadd~/git_homework[master !]$ git commit -m 'Add text in quotes.txt' [master 90a3e1f] Add text in quotes.txt 1 file changed, 2 insertions(+) virginialadd~/git_homework[master]$ git status On branch master nothing to commit, working tree clean virginialadd~/git_homework[master]$ oneline -bash: oneline: command not found virginialadd~/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)
  • empty (boolean)

Methods:

  • break_down
  • stack
  • fall_apart
  • be_filled

4. Questions/Comments/Confusions

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

  1. Hopefully the one line was submitted correctly. I used an outside source. Is there a way for terminal to print a one line log?

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.

@damwhit
Copy link

damwhit commented Aug 22, 2019

@vladd-png yes! git log --oneline

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