Skip to content

Instantly share code, notes, and snippets.

@sashajustice
Last active January 9, 2018 23:31
Show Gist options
  • Save sashajustice/8afdda04a6f9aba384cbf0dff627d507 to your computer and use it in GitHub Desktop.
Save sashajustice/8afdda04a6f9aba384cbf0dff627d507 to your computer and use it in GitHub Desktop.
Work Plan January 8, 2018
# **Overview**
This week's focus will be a similar preparation for the Practice phase interview with more of a focus on test simulation practice.
# **Areas of Focus**
SQL
work through Challenges 1,3,4,5, in Bonnie's pets challenge
GET routes
work through Challenge 3, 7,9,10,11 in Bonnie's pets challenge.
read the Express docs for GET routes.
Implementing handling for route, rendering to pug/ejs/etc
#**DOM Manipulation**
-adding and removing a picture
-changing colors of page
-removing elements
-changing text on a page
Live coding simulation
-Try to meet with a coach everyday where I'm typing in front of them
-Pair with someone and code /trade turns where one is watching
**Algorithms**
Improve problem-solving skills, thinking faster
-Do one code wars or reddit problem a day
# **WorkPlan**
Work through samples multiple times
Watch youtube dom tutorials
Review practice samples, write new solution from scratch
Sample test session @[](url)
@Moniarchy
Copy link

Hey Sabrin! Here's what your gist should look like, an update from our meeting with Bonnie.

Foundations Phase Work Plan

  • Do your best to finish your work plans by end of day Mondays. It's better to have a more detailed work plan that you get done later in the day than having a half-assed work plan. The first time/couple times you do it it might take more than a day!
  • Gists should be properly formatted .md files. Here's a link to markdown formatting information.
  • All work plans should have 3 sections Overview, Areas of Focus & Study Plan

Overview & Weekly Goal

  • This is a short 1-3 sentence overview of what you'll accomplish this week.

Area of Focus

  • An area of focus is ideally based off of the feedback you received from an SEP from a previous test. It is an idea of a related set of work that you need to improve upon.
  • This section should include any links to the external projects that you are going to use to support your growth in these areas.

Study Plan

  • The Study Plan is your engineering to do list. They have a ton of detail and it's where you do your heavy thinking for the week. Once your study plan is complete you should be able to focus on code.
    • If, for example, you're using Bonnie's pets challenges
      • create a function takes two parameters: pet name and species name.
      • The function has a query that looks up the id for the species.
      • The function has another query that adds the pet using the species id.
      • The function returns a Promise that resolves to the id of the new pet.
      • etc ...
  • You should be 90% sure that you can get through your specs inside of this week. Don't over or underestimate what you can get done, try to hit the nail on the head!

@sashajustice
Copy link
Author

Overview

This week's focus will be a similar preparation for the Practice phase interview with more of a focus on test simulation practice.

Areas of Focus

SQL
work through Challenges 1,3,4,5, in Bonnie's pets challenge
GET routes
work through Challenge 3, 7,9,10,11 in Bonnie's pets challenge.
read the Express docs for GET routes.
Implementing handling for route, rendering to pug/ejs/etc

#DOM Manipulation

-adding and removing a picture
-changing colors of page
-removing elements
-changing text on a page
Live coding simulation
-Try to meet with a coach everyday where I'm typing in front of them
-Pair with someone and code /trade turns where one is watching

Algorithms

Improve problem-solving skills, thinking faster

-Do one code wars or reddit problem a day

WorkPlan

Work through samples multiple times
Watch youtube dom tutorials
Review practice samples, write new solution from scratch
Sample test session @

@sashajustice
Copy link
Author

Here's my latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment