Skip to content

Latest commit

 

History

History
71 lines (34 loc) · 4.91 KB

week-09.md

File metadata and controls

71 lines (34 loc) · 4.91 KB

Week 9

The evening trainings and readings below will help you solidify work so far and/or prepare you for the next day's materials.

Monday

link to submit tonight's pulse check: your bog app repository (remember to update the README on the master branch as described in the submission instructions)

  1. Work through part 1 of the Rails Pet Lab.

  2. Check out the Active Record Validations Rails guide:

  • Read chapter 1 closely.
  • Skim through chapters 2 and 3. Pick two methods from chapter 2 and implement them in the pet lab.

Tuesday

link to submit tonight's pulse check: your pet lab repo, link us to the branch you used last night to work on part one.

  1. Work on the rails pet lab focusing on parts 2 and 3 for at least two hours. If you have finished parts 2 and 3 within 2 hours, spend some time on the challenges from part 4.

Wednesday

link to submit tonight's pulse check: the most complete branch of your pet lab

  1. Complete part 1 of the Library App. You'll work on part 2 tomorrow morning.

  2. In preparation for tomorrow afternoon, read the asset pipeline rails guide, sections 1 and 2.

As you read, jot down answers to the following questions in your own words:

  • What is fingerprinting, and why should I care?
  • Why does the order of the files listed in the manifest matter?
  • How should I use helper methods to include image assets in my HTML?
  • How should I use helper methods to include image assets in my CSS?
  • I want to use an external library that doesn't have a gem. Where should I put the library's code (what directory)?

Thursday

link to submit tonight's pulse check: your library app repo (and your driver's name, if you don't have the most up-to-date code you worked on)

  1. Work through the asset pipeline exercises, including the non-bonus portions of the asset pipeline poem lab and additional challenges. When you complete the app, slack out one tip that might help others who are stuck, in the group slack channel.
  • When you want to precompile, consider starting a branch to try that out. You can see the effect and then switch back to your main branch.

  1. Complete the non-bonus portions of the Library Application, part 2. When you complete the app, slack out one tip that might help others who are stuck, in the group slack channel. Instructions for the authorization part have been improved, on the class copy of the repo: updated authorization section.

  2. Review rspec by completing the Car class tests for part 1 of this Rspec Racer training. When you run rspec spec/car_spec.rb, you should see all 3 tests you filled in passing.

Weekend

link to submit tonight's pulse check: your asset pipeline poem repo and cars repo links

  1. Come up with a project 2 pitch for a Rails CRUD app that could fulfill these technical requirements. Spend some time sketching out your idea to include the stages of progress the application could move through from skateboard, to scooter, to bicycle, etc. Remember, you will be working on this project with a 4 person group over the course of a week. Your pitch will be brief with no slides, but we want you to hit the ground running with some more detailed ideas sketched out.

  2. Prepare a technical lightning talk on a Ruby gem of your choice.

Outcomes Homework

Due Wednesday 5/31

Research 3-5 websites you like and note the design AND BRAND for ideas towards your portfolios. Do not mix designs if they don't go well together; notice also the aesthetic that brings the design elements together. Pair of up with a UX Design student as needed for feedback and ideas towards designing your portfolio.