Mills' intermission work

Mills Provosty

Make a copy of this gist to your GitHub account. In your gist, please answer the questions in the first three sections, then complete the techincal work. Please provide any relevant links inside your gist!

**Organization Systems** (if your answer to any of these is `none` - let's change that! If you need help finding something, let the group know and we can brainstorm):
- What tool/system to you use to track your to-do list?
Trello!
- What tool/system do you use to calendar your time and ensure you remember appointments, deadlines, etc?
I use google calendar and set alamrs. 
- What do you use for a timer for worktime/pom breaks?
Timer on my phone. 

**Life Stuff:**
- Do you have a good meal prep or eating/cooking plan? What is it?
I do! I use Blue Apron- have been for about 2 years now. Love it. 

- Do you have exercise needs? If so, do you have a plan to fit that in your schedule?
I do Orange Theory Fitness 3-5 times a week.
- Do you have any distractions or time-sucks that need to be eliminated? (Instagram, FB, etc)
Driving. I need to work harder on organizing my time and planning for the whole day so I don't need to stop at home and get things.

**Mentor/Upper Mods:** (We would like you to have one dedicated mentor that you plan to meet with weekly to pair. You can absolutely also talk, vent, etc. with them or a different mentor):
- Who is your mentor that you will meet with weekly for pairing?
Right now I meet up with Mike Dao every week. 
- Weekly meeting time/day: 
We haven't set that up yet, I will check in!
- Who is (at least) one person from Mod 2 or 3 that you feel comfortable to reach out to for help if/when needed? 
EVERYONE! Jalena, Blake, Carrie, Smitha, Matt L, Matt W....everyone. 
**Technical Prep/Practice:**

While working: Set your pom timer for 25-45 minutes. Before you start working, write down in your notebook your goal/focus for that chunk of work time. When the timer goes off, log what you completed in relation to your goal (and/or if you got distracted?!) then TAKE A POM! Repeat!

1. Practice keyboard shortcuts. You should be fluent using...
    * command + tab (mac)
    * command + c / command + v (atom/chrome)
    * command + x (atom)
    * command + (any arrow - atom/chrome)
    * command + control + (up or down arrow - atom)
    * command + shift + ([ or ] - atom/chrome) 
    * fn + delete (mac)
2. Exercises - up to you - hashes, enums, ruby, old Independent Challenges.
3. Complete [Dog Walker Challenge](https://github.com/turingschool-examples/dog_walker)
   * [Link to your repo](https://github.com/MillsProvosty/dog_walker)
4. Complete [Credit Check](http://backend.turing.io/module1/projects/credit_check). Read the entire project spec before starting, and do not feel like you need to follow the order of iterations. In fact, you should probably use TDD so do Iteration 3 as you go. (This has been used as the Week 1 project in the past which is why that is later!) After you finish, check out to an `annotation` branch, and annotate each line of code. I know this sounds tedious but you should get SO MUCH out of it! Find an example annotated class/test [here](https://github.com/ameseee/annotation_example).
   * [Link to your master branch](https://github.com/MillsProvosty/credit_check)
   * [Link to your annotated branch]()