Session 1 HW

CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Readings + Responses

1. Do Experienced Programmers Use Google Frequently? by Umer Mansoor (10 min)

• Your key take-aways OR how you're going to implement specific points (minimum 2):
• Googling can and should be used for validation of a developer's logic as well as for information and guidence.
• Use concise search queries and perform multiple searches if necissary.

2. 20 Google Search Tips to Use Google More Efficiently by Joseph Hindy (15 min)

• Briefly describe (in your own words) each of the tips below AND provide an example of a search that captures the sentiment of the tip
• Tip 2: Searching with quotes searches for the exact words in the quotes rather than a collection of words. EX: "maple tree care" vs maple tree care. The second querey might provide results for tree care not specifically "maple tree care"
• Tip 3: Use hyphens to exclude word meanings. EX: Shift- keyboard would exclude all search results with keyboard in the result.
• Tip 4: Using colons to search for results from a particular site. EX: Removing the last element of an array site:developer.mozilla.org
• Tip 9: Search multiple phrases or words that could yeild desired results using quots and OR keyword. EX: "best coding practices" OR "essential coding practices"
• Tip 13: Phrase searches in language that websites use. EX: How do I make chocolate chip cookies without eggs vs eggless chocolate chip cookie recepie.
• Tip 14: Boil down searches to just the most important words. EX: How do I find the length of a string in Javascript vs find string length Javascript.
• Tip 17: Think about synonyms for words or other ways that a search might be described. EX: "Door won't open Toyota Tacoma" OR "Door Repair Toyota Tacoma"

Turing Prep

1. Creating a Mod 0 Calendar (20 mins)

Before you create your Mod 0 calendar, we recommend going back to the Session 1 Lesson to review some tips from our most successful students re: calendaring and time management.

Create a calendar using a tool of your choice (Google Calendar, iCal, etc.) for the remainder of Mod 0 until your due date for the Mod 1 Prework. Your calendar should include the following:

• Each class session
• Relevant due dates: HW, Assessment submission, Mod 1 Prework, Cohort Orientation
• When do you plan to work on HW?
• When do you plan to work on the Mod 1 Prework (about 40 hours total)?
• When do you plan to review material covered in class?
• When do you plan to study for the assessment?
• When do you plan to make time for self-care?
• What other commitments do you have throughout the course of Mod 0?

As outlined in class, using different colors in your calendar for parts of your life (Turing, wellness, commitments, etc.) can make it easier to parse through your competing priorities. Here is a suggestion you could use for your Mod 0 Calendar...

• Mod 0 classes
• Outside prep (HW, Prework, studying, practice, assessment)
• Work/prior commitments
• Wellness

Take some time to build out your calendar for Mod 0 and add a few photos/screenshots below. You can take a screenshot on your Mac using CMD + SHIFT + 4 and drag around the area of your screen you want to capture!

The first answer in this StackOverflow post gives a great shortcut for easily adding images to your gists!

⬇ Add screenshots of your calendar below ⬇

**If you are struggling to find time in your calendar to complete all of the M1 Prework please reach out to Eric Weissman (@ericweissman) on Slack to setup some time to discuss an alternate gameplan for completion!**

Exercises

1. Creating Files and Directories (10 min)

Need help? You can go back to the files/directories portion of the lesson here.

Use commands in your terminal to create the directories and files structured exactly how they appear in the image below.

When you're done, type history to see your commands. Copy and paste the commands that were used to create the directory and files:

   53  clear
   54  mkdir cool_project
   55  cd cool_project
   56  touch README.md
   57  touch styles.css
   58  mkdir dank_codes
   59  cd dank_codes
   60  pwd
   61  touch data.rb
   62  touch app.js
   63  mkdir resources
   64  md resources
   65  pwd
   66  is
   67  ls
   68  md resources
   69  cd resources
   70  deployment.md
   71  touch deployment.md
   72  mikdr utils
   73  mkdir utils
   74  cd utils
   75  touch utilities.md
   76  history

MacBook-Pro:utils conorbarthel$

2. 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$'

After you have saved this file, be sure to quit and restart your terminal.

We will be working more with git in the next session and will be able to see some of these changes take effect!

4. Practice Keyboard Shortcuts (10 mins)

Mac Environment

Use these shortcuts to quickly move around within your environment.

• command + spacebar - Open a program or search for a file
• command + tab + tab ... - Cycle through open programs
• command + ~ - Switch between separate open windows of the same program
• command + q - Quit an open program

Rectangle

Start by making sure Rectangle is running with command + spacebar then type rectangle and then return. You should see a window icon at the top right of your menu bar. Click the icon to see a dropdown of your shortcuts. Click preferences to customize them.

• command + option + enter - Full Screen Current Window
• command + option + left arrow - Left Half Current Window
• command + option + right arrow - Right Half Current Window
• command + option + up arrow - Top Half Current Window
• command + option + bottom arrow - Bottom Half Current Window

Chrome Browser

Start by opening Chrome with the shortcut (command + space) you already learned.

• command + d - Bookmark current page
• command + t - Open new tab
• command + n - Open new window
• command + shift + n - Open new window in Incognito mode
• command + l - Highlight current URL
• control + tab - Cycle through tabs to the right
• control + shift + tab - Cycle through tabs to the left
• command + shift + r - Reload page
• command + w - Close tab

This video from Technical Programs Instructor Amy Holt gives some great screen management tips.

Self Assess

Using the rubric below, assess how you did with these exercises. These are the same metrics your instructors will use to determine if you are prepared for Mod 1!

• I read carefully read ALL directions
• I completed all parts of the exercises (not including Extensions) to the best of my ability
• I used correct syntax, spacing and naming conventions
• I followed ALL formatting instructions
• I pushed myself out of my comfort zone and experimented/broke things to try to learn
• I spent no longer than 20-30 mins Googling a specific problem before asking for help
• I went back to the lesson to search for clarification before asking for help

Stuck? Having Issues?

Are you stuck on something? Here is the BEST way to ask for help:

• Start or reply in the thread with the problem you are facing. Be sure to follow the guidelines for asking questions below:
  • I can explain what I am trying to do or accomplish
  • I can what I have tried so far and/or what resources I've tried online
  • I can describe specifically what I am stuck on
  • I provided screenshots and/or code examples to give context
    • If I provided short code examples, I used inline code formatting for single lines of code/error messages
    • If I provided larger blocks of code, I used a code snippet in the correct format (such as .js or .rb)
• Usually, your classmates will be able to answer your question or point you in the right direction very quickly! If not, an instructor will reply within 24-48 hours