jbracht

Flexbox

"Flexible Box Model" - aims to provide a more efficient way to style pages

• Items contained inside a flex container with "flex" to best fit the available space.
• Flexbox layout is direction-agnostic making it more flexible than other layout models (block layout being vertically-biased, and inline layout being horizontally-biased).
• Flexy layouts are responsive – they will grow/shrink as specified to fit different screen sizes

Terminology

jbracht

Track 1 - Ruby on Rails	Track 2 - Programming Paradigms
Alex Mann	Ahsun Kim
Alex Mok	Alena Ioffe
Allison Geismar	Arnald Wong
Alyona Rodina	Asia Gagnon
Amaris Chang	Audra Kenney
Amneet Sandhu	Colleen Higgins
Cara Takemoto	Daniel Rivera
Chang (Sunny) Mei	Dyane Ramos

jbracht

Realtime Games	TypeScript, SASS, & Workplace Ethics	Design Patterns & Scale
Abu Islam	Aaron Nah	Bianca Czaderna
Allie French	Alex Grazier	Charlyn Manuyag
Amy Liao	Aly Norrgard	Chelsi Asulin
Billy Tan	Ann Kettles	Christina Armstrong
Brook Li	Anna Mai	Christopher Najafi
Daniel Kil	Ariel Ahdoot	Conrad Batraville
Daniela Mead	Baz	Daniel Lanoff
Danny Marquez	Be

jbracht

About Senior Checkpoint:

What it is for:

• Diagnosing if you're ready to put together Senior Phase projects
• The biggest question we're trying to ask with this test is: can you write a single page CRUD (create, read, update, delete) app?
  • if so, you'll be able to start working on larger scale projects

Format:

• Spec-based
• It'll look a lot like your Pillars Checkpoint

jbracht

Pairing with git

Getting started

You and your partner should follow these instructions together. "PartnerA" will assume the role of "driver" first, and "PartnerB" will assume the role of "navigator" first - decide now who those will be. You should switch these roles every 15 minutes (use a timer to keep track).

The steps below will help you establish a workflow for sharing your work with each other using Git. Note that for this to work, it is very important that only one partner works on the project at a time - you must stick to the driver/navigator roles.

• Both partners should fork the repo and clone their fork to their respective machines.
• PartnerA: Copy the url for your fork's github page from your browser's url bar (it will be something like https://github.com/<PartnerA_username>/<PairExercise.WorkshopTitle>) and send that url to PartnerB via Slack
• PartnerB: Copy the url that PartnerA sent you, cd into your local clone on your machine and execute this command using that url:

jbracht

Allowed:

• Student Notes (including notes on workshop code)
• Documentation
• Lecture slides
• Demo code samples
• Notes students share with one another
• Help tickets (esp in case of specs not running or very basic clarification needed)

Forbidden:

• Workshop code

jbracht

ORM: Object Relational Mapper

• backend
• Ex: Sequelize!!!!
• Allows us to talk to our DB
• Tables = classes, rows = instances/objects

Middleware

• backend
• In web dev: runs between REQUEST & RESPONSE
• Ex: morgan, express, body parser