aspitz1/session1_hw_mod0.md

## session1_hw_mod0.md

      
    Raw
  

              session1_hw_mod0.md
            
          
    Session 1 HW

CAREFULLY READ ALL THE INSTRUCTIONS BEFORE STARTING THESE EXERCISES!
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 edit a Gist multiple times.

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):
There is no need to try and memorize every line of code when you can use Google.
You don't need to have all the answers. You do need to research something you are questioning.
Part of being a successful programer is being able to learn new things via self led research on Google.
Be sure to use trusted sources and take from many different places.
Make a lot of searches using different terms. Frequently the types of search terms you use will evolve as you gather more information.

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: If you put quotes around a phrase it tells Google to search for that exact phrase

Example "fastest runner alive"


Tip 3: Use a hyphen to tell Google what not to search for in an ambiguous word

Example date -fruit


Tip 4: Use a colon to search within a specific site

Example tuition site:turing.com


Tip 9: You can search for multiple things at once using OR

Example:plantains OR bananas you can also use a phrase like "can birds fly in the rain" OR "can fish see"


Tip 13: Use phrases and words that websites would use, think print adds

Example: instead of I need a haircut try hair salons


Tip 14: Use only the important search terms

Example: instead of place on that one corner that has burgers try burger restaurant near me


Tip 17: Use words that describe what you're looking for

Example: instead of dog try dog hunting breeds


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 0 Project. Your calendar should include the following:

 Each class session
 Relevant due dates: HW, Mod 0 Project, Tuition, Cohort Orientation
 When do you plan to work on homework?
 When do you plan to work on the Mod 0 Project (about 35 hours total)?
 When do you plan to review material covered in class?
 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, Project, 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. Please provide screenshots of the weekly view, not monthly view, so we can easily see the actual time allotment to each event. You can take a screenshot on your Mac using cmd + shift + 4 and drag around the area of your screen you want to capture!
This video walks you through how to add a screenshot to a GitHub Gist!
⬇ Add screenshots of your calendar below ⬇


I use Goodle calander for more of a macro view of my days


I use Structured for a micro view of my days. Structured doesn't provide a week view, it is just day by day. I plan as far ahead as I can but didn't want to include too many screen shots to show a whole week. Inside each block is space to add details. I'll work on continuing to break down my blocks of time even further.


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:
  60  mkdir dank_codes
   61  cd dank_codes
   62  touch data.rb
   63  touch app.js
   64  ls
   65  mkdir resources
   66  cd resources
   67  deployment.md
   68  touch deployment.md
   69  ls
   70  mkdir utils
   71  touch utilities.md
   72  ls
   73  mv ~/cool_project/dank_codes/resources/utilities.md ~/cool_project/dank_codes/resources/utils/utilities.md
   74  cd utils
   75  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!
3. 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. Make sure you know the shortcuts to do the following:

Full Screen Current Window
Left Half Current Window
Right Half Current Window
Top Half Current Window
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

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 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 explain 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

Submission

There is no actual "submission" of this assignment; if you forked it from the original gist and saved your changes on your fork, we will be able to see your work. You do not need to send a link to us. One way you can check that you forked correctly is by going to the original gist the homework assignment was written in. Click on "Forks", then look through the list (you may want to use cmd + F to open the search bar within the browser). If you see your GitHub username, that means your instructors see it too! On the far right, you can click the "View Fork" button to view your work.