Got a request from Claudia to cover removing event listeners after a pairing session with Mike Pack. Seems reasonable.

Not sure if we should be updating the MDN repo that we've been working from or should start porting things over to Turing so we have more control over the content...

This is a intermediate step before the order is actually placed and written to the table

As a user
When I have items in my cart
And I click "Checkout"
I am redirected to a page for selecting a "Pickup" time
I see a list of 1-hour slots to pickup my order (10 am - 3pm)
And I check a box to select a time for pickup
And I click "Reserve"

** Temporary "Confirmation" Show page **
I am redirected to a Confirmation page which shows:
The current order, and the reservation time

Skylight does not consistently respond in a timely manner. Kind of a bummer.

https://github.com/turingschool/lesson_plans/blob/master/ruby_04-apis_and_scalability/load_testing_and_production_performance_monitoring.markdown

change this example to be more accurate

 Array.prototype.strangePet = 'snake';

var myPets = ['dog', 'dog', 'rock'];
for(var i in myPets){
  console.log(i);
  // You will see 'snake' show up in your list of pets
}

I'm thinking that moving the notes directly into the lesson plan almost like a tutorial would be nice.

What do we consider a pending invoice?

Can we cover more fundamentals, like "everything is an object"

Still just a bullet point lesson. Needs to be fleshed out, and potentially we're going to add TDD to it. Or maybe add TDD to the lesson. Or make the TDD in testing better. Or remove VCR. Still need some work here.

New assessment procedure

Either need to use the actual assessment, instead of mock, or we need to flesh out the mock. The current mock assessment has vague specs, and an incomplete rubric. We need to have clear specs and rubric so we can grade more strictly.

General comment - but the current points system needs to be re-worked/wrangled as it's currently too heavily weighted on projects that tend to be graded lightly - and with mock assessment not being factored in...

Needs explanation and example code

in Destination Planner

Still just a bullet point lesson. Needs to be fleshed out, and potentially we're going to add TDD to it. Or maybe add TDD to the lesson. Or make the TDD in testing better. Or remove VCR. Still need some work here.

In the mod3 Readme, the Friday session for week 4, Using PORO's in Rails, links to the lesson archive/presenters_and_decorators.md.

Update the link when the lesson plan for Using PORO's in Rails is written.

During scale up, students are doing a lot of their own research. Turing has a lot of old lessons that we don't teach anymore, but could be relevant to their scale up.

We have a separate markdown file for each scale-up project. Do we need that? There is a lot of copied content between each one. They even have the same rubric.

Include regex101 - regex crosswords as homework

The Ajax class uses jQuery's .delegate() method which was depreciated a few versions ago. This should be updated to use jQuery's .on() method.

http://api.jquery.com/delegate/
http://api.jquery.com/on/

We had a couple lessons that went to the archive on using presenters, decorators, and alternatives to using callbacks at the model level. We probably need an hour and a half for this.

Areas to consider:

• How can we clean up views using presenters?
• What is the decorator pattern and how do we implement it with Ruby?
• When discussing alternatives for callbacks, focus on the problems that callbacks can cause (e.g. after_save can reach into other tables and update data that we can easily forget about leading to unintended consequences.)

What? - Update the M3 README to include the common day to day tasks that are done during the module and the person responsible for taking care of them.

Example:
Clean fake mustaches: Josh
Bring in Swedish candy: Lovisa
Explain Pokemon: Tess

Why? - Make it easier when rotating or on boarding staff members to know what tasks need to be taken care of. Make it clear to students who they should bring their concern about a specific item to.

Markdown is hidgeous - would be nice to clean up the formatting here so assignment is less confusing

https://github.com/turingschool/lesson_plans/blob/master/ruby_04-apis_and_scalability/job-hunting-assignment.markdown

Need to meet with Allison to coordinate

a great place to merge soft skills into the daily course work. Maybe we could do a 1 hour lesson on technical blog posting and do some reviews for the posts.

Sinon is apparently not playing well with webpack. Would phantomjs?

We're going to have students review their medium posts as well as their code

We spend all this time diagramming the oauth handshake, and then have them just use a Gem. I feel like they aren't getting the diagram. Maybe if the instructor coded the handshake manually, it would make it more concrete. And then they implement a Gem.

https://github.com/turingschool/lesson_plans/blob/master/ruby_04-apis_and_scalability/client_side_storage.markdown

• Flesh out example repo for localStorage strategy
• Update README in example repo
• Add section about API keys and security
• Implement Firebase section of example repo in Node?
  • Storing API keys in Node?
  • Update outdated links and content in lesson plan
• Node and Postgres Branch

Some lesson plans have broken links to resources. I think some of these occurred when we migrated from Dropbox to Drive.

For now, w'ere gonna keep the old discussion at the top, give them some resources, and then have them get selenium up and running.

Nice to have: Some examples to run, and gotchas

There's some broken links, and links to old stuff

Not 100% sure this is a problem, but I want to make sure the links to lesson plans are correct and that the structure for the module accurately reflects the current state. There may be new links to be added as well e.g. Assessment.

More students used fixtures this time around, but were frustrated with setting up relationships. Probably because we didn't teach that. That would be a good idea.

Currently exists as bullet points for a discussion

Should be fleshed out as an actual lesson which leads into completing pizza express

A stretch goal would be to walk through replicating the starter kit for Webkit in Node with a basic game. Wouldn't replace pizza-express because that wouldn't give us routing per se...

Something to help instructors and students set a rough agenda for their check-ins.

The last time I taught the AJAX lesson, we spent a lot of time debugging. Mod 3 students just don't have much experience debugging javascript. I'd like to add a small intro to Javascript debugging. We can probably borrow content from the M4 lesson on JS Debugging

Rewrite consuming API lesson to be more of a tutorial. https://github.com/turingschool/lesson_plans/blob/master/ruby_03-professional_rails_applications/consuming_an_api.md

Use case is not clear

Concept of Require homework should probably reference the import syntax in ES6 in some way

https://github.com/turingschool/lesson_plans/blob/master/ruby_04-apis_and_scalability/assignments/the-concept-of-require.markdown

There are links to lesson plans that are broken.

Instagram has changed their API and it's kind of cumbersome. Tumblr uses an old version of oauth. Let's add some others, like Meetup, Flickr, Twitter, Spotify, Strava

Outline incoming. I'll add it as a comment soon. I think I'd like to teach this some time next week. This should be 30-60 minutes worth of content.

Thinking about replacing VCR with standard mocking and stubbing to give students more control and a better understanding of how to mock and stub.

Controller tests are maybe being deprecated