saylerb

#!/bin/sh

# Git proxy settings
echo "Configuring Git..."
git config --global http.proxy http://gateway.zscaler.net:80/
git config --system http.proxy http://gateway.zscaler.net:80/
git config --global http.sslVerify false
git config --system http.sslVerify false
git config --global --unset http.sslcainfo
git config --system --unset http.sslcainfo

saylerb

##PROTIP: README Love

READMEs are AWESOME. They are one of the best things you can add to a repo, (other than quality code), to make it look professional.

####Things that make a README great:

• A link to the production site on heroku
• A screenshot (or a few) of what the app does (This is especially important if you don't have the production app up and running yet)
• Directions on how to clone or fork the repo and run it locally (explain it like you're explaining things to a totally new programmer)

saylerb

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

###Array ####Definition:

• Stores data elements based on an sequential, most commonly 0 based, index.
• Based on tuples from set theory.

saylerb

Cubby Stuffers

Pitch

A subscription-based snack service for students who are not always on top of their grocery shopping game.

Problem

There is no access to food at Turing unless you bring it. This can be a daily struggle that can also cost you a lot of money in the long run. Yes you can save on costs by buying your own snacks at the store and bringing them everyday. If you are that productive of a human, this service may not be for you. Get your cubby stuffed with delicious snacks for the week every week on a subscription-based snack service.

saylerb

# This is a skeleton for testing models including examples of validations, callbacks,
# scopes, instance & class methods, associations, and more.
# Pick and choose what you want, as all models don't NEED to be tested at this depth.
#
# I'm always eager to hear new tips & suggestions as I'm still new to testing,
# so if you have any, please share!
#
# @kyletcarlson
#
# This skeleton also assumes you're using the following gems: 

saylerb

1. Define CRUD.

• Create, Read, Update, Delete. Gives us all the behavior to make a fully-functional web application

2. There are seven verb + path combinations that are necessary in a basic Sinatra app in order to provide full CRUD functionality. List each of the seven combinations, and explain what each is for.
3. GET "/tasks" - displays all the current tasks with the :index view
4. GET "/tasks/:id" - display a single task with the :show view
5. GET "/tasks/new" - display the form to create a new task with the :new view
6. POST "/tasks" - write a task to the database, and redirect back to "/tasks"
7. GET "/tasks/:id/edit" - display the form for editing an existing task with the :edit view
8. PUT/PATCH "tasks/:id" - update a specific task in the database with new data, and display the edited task by redirecting back to "/tasks/:id"

saylerb

Introduction to Sinatra

1. What is the purpose of the server file (routing)?

• The server file contains the routes for specific HTTP verbs, and determines what the client gets back with each request

2. How do you pass variables into the views?

• Two ways
• Using an instance variable:

saylerb

Turing School Prework

Task A- Practice Typing:

• screenshots of scores will be posted in comments

Task B- Algorithmic Thinking & Logic:

• screenshots of completed sections will be posted in comments

Task C- Create your Gist: