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):
• Although I was well aware google was essential to programming, I underestimated how much it would be utilized.
• Starting off with a tutorial for a programming medium you're unfamiliar with before even beginning to work seems like a good idea.

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:
• Utilizing quotes correctly is an important part of successful google searches. This is especially true if one of the words in your search is common. If I were to search with the keywords 'Slack' and 'thread' without putting a specific search phrase in quotations, I might get websites on how to sew. I need to use quotations to associate the two words together in googles search so I can narrow down the scope of subject and remove the riff-raff.
• Tip 3:
• Hyphen is another useful tool to narrow down search results and negate results you do not want. Again using the example above, I can search for Slack and Thread and negate sewing search results with a -sew and ensure I'm only getting relevant results.
• Tip 4:
• Once we establish a set of websites that we are continuously referencing for our programming or preticular language we're using, we can use the colon feature to only search in those specific websites. For example, if I were searching for the proper way to randomize numbers in javascript, I would most likely use the mozzilla developer website so my search might be something like 'math random javascript : developer.mozilla.org'
• Tip 9:
• Adding phrases together can help your searches be successful when you're not entirely sure the best phrase to search or when you're searching for different things and are trying to establish their connection/correlation.
• Tip 13:
• In today's internet, blogs, opinions, and social media drives most of the traffic. In order to help filter to more professional websites instead of personal drivel, it's important to alter your terminology appropriately. In the examples provided, using "headache relief" instead of "my head hurts" would allow you to find medical websites and not someone's facebook post complaining about their headache.
• Tip 14:
• Filtering out unneccesary words in your searches will keep your results relevant and concise so google's algorithms aren't triggered by filler.
• Tip 17:
• Keep in mind you can reword your searches with different terminology to help get different results. This is especially useful when you're unsure of the correct terminology.

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:

   93  mkdir dank_codes
   94  list
   95  ls
   96  cd dank_codes
   97  pwd
   98  touch data.rb
   99  touch app.js
  100  mkdir resources
  101  ls
  102  cd resources
  103  pwd
  104  touch deployment.md
  105  mkdir utils
  106  cd utils
  107  touch utilities.md
  108  ls

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