Mod 0 Session 2 Practice Tasks

mod_0_session_2_practice_tasks.md

Session 2 Practice Tasks

The assignments listed here should take you approximately 55 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:

  163  mkdir terminal_practice
  164  cd terminal_practice
  165  pwd
  166  touch favorite_foods.txt
  167  ls
  168  atom .
  169  ls
  170  cat favorite_foods.txt
  171  rm favorite_foods.txt
  172  ls
  173  cd ..
  174  ls
  175  rm -rf terminal_practice
  176  ls
  177  mkdir session_3_practice
  178  cd session_3_practice
  179  touch budget.csv mentors.txt
  180  mkdir notes practice
  181  cd notes
  182  touch git_notes.txt command_line_notes.txt
  183  cd ../practice
  184  mkdir projects
  185  touch git_practice.txt
  186  cd projects
  187  touch game.js

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):

 piknikki@Nikkis-MBP  ~  mkdir git_homework
 piknikki@Nikkis-MBP  ~  cd git_homework
 piknikki@Nikkis-MBP  ~/git_homework  touch quotes.txt
 piknikki@Nikkis-MBP  ~/git_homework  git init
Initialized empty Git repository in /Users/piknikki/git_homework/.git/
 piknikki@Nikkis-MBP  ~/git_homework   master  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)
 piknikki@Nikkis-MBP  ~/git_homework   master  git add quotes.txt
 piknikki@Nikkis-MBP  ~/git_homework   master ✚  git commit -m "initial commit"
[master (root-commit) 2ea2d37] initial commit
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 quotes.txt
 piknikki@Nikkis-MBP  ~/git_homework   master  git status
On branch master
nothing to commit, working tree clean
 piknikki@Nikkis-MBP  ~/git_homework   master  git status
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
d41937d (HEAD -> master) added new quote
2ea2d37 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 (15 min)

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)
• labels (array)

Methods:

• breakDown
• stack
• attachLabels
• tapeClosed

4. Modify your Zsh Prompt (10 min)

• Make sure that your shell is set to zsh by running the following command: $ chsh -s /bin/zsh. Remember to omit the $! Note that macOS Catalina and later operating systems already use zsh as the default shell.

• Watch this video and follow each step to modify your own zshrc configuration file. As mentioned in the video, you will need this snippet below:

# Load version control information
autoload -Uz vcs_info
precmd() { vcs_info }

# Format the vcs_info_msg_0_ variable
zstyle ':vcs_info:git:*' formats '%b'

# Determine if current working directory is a git repository
git_branch_color() {
  if current_git_status=$(git status 2> /dev/null); then
    parse_git_dirty
  else
    echo ""
  fi
}

# Change branch color if working tree is clean
parse_git_dirty() {
  if current_git_status=$(git status | grep 'Changes to be committed:\|Untracked files:\|modified:|deleted:' 2> /dev/null); then
    echo "%F{red}"
  else
    echo "%F{green}"
  fi
}

# Set up the prompt (with git branch name)
setopt PROMPT_SUBST
PROMPT='%F{white}%d $(git_branch_color)${vcs_info_msg_0_} %f$'

5. Questions/Comments/Confusions

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

1. I didn't use syntax highlighting here because it's command line.

Extensions

1. This course is how I personally learned command line. If time permits, I highly recommend reading and practicing.

2. Also recommended by Jeff Casimir: Michael Hartl's Learn Enough Command Line.

z_img_1.png

I didn't use syntax highlighting on this one because I couldn't find a tag for it. Please let me know what to use instead of javascript if there is one for command line comments. Thx.

@piknikki no worries, syntax highlighting is a nice to have, but not necessary in all cases. Solid work on this! What attributes would your methods utilize or affect and how?

@damwhit -- thanks. See below to answer your question (thanks for making me think harder about this):

Attributes:

width (integer)
depth (integer)
color (string)
labels (array)
numberBoxesInStack (integer)
isClosed (boolean)

Methods:

breakDown: decrease width and depth integers
stack: increase numberBoxesInStack integer (I added the attribute because what I had didn't make sense)
attachLabels: add string to labels array
tapeClosed: changes isClosed boolean. (also added a new attribute)

Love it!