Skip to content

Instantly share code, notes, and snippets.

View gprocell927's full-sized avatar
🏔️

Gabi Procell gprocell927

🏔️
  • Denver, CO
  • 21:27 (UTC -06:00)
View GitHub Profile
@gprocell927
gprocell927 / cold-outreach-worktime.md
Last active April 20, 2017 21:18
Cold Outreach Worktime
@gprocell927
gprocell927 / commit-etiquette.md
Created October 31, 2016 15:31
Proper Commit Message Etiquette

Rules For Proper Commit Messages

  1. Short, concise, descriptive messages.
  2. Written in imperative mode (uses "Fix", "Add", "Change")
  3. The first line should always be 50 characters or less and it should be followed by a blank line.
  4. Message states why the change was necessary, and what side effects it may have.

Examples of Good Messages

Fix failing ButtonTests

@gprocell927
gprocell927 / accessibility-commitments.md
Created October 3, 2016 17:06
Accessibility Commitments
  1. Be adamant about utilizing semantic HTML.

  2. Design so that the user knows where they are on the page at all times.

  3. Design so that the user is engaged in the site, but also has a clear idea of how to navigate the page.

@gprocell927
gprocell927 / gabi-procell-css-layout-challenge-solutions.md
Last active August 28, 2016 23:07
CSS Layout Challenge Solutions
Challenge Number 1

Description of approach: We used a container to wrap the div2 and div3 elements so that we could display the elements as an inline block and float them to the right as one unit. Challenge number

Challenge Number 2

Description of approach: After much struggle, we learned that this challenge needed to make use of margin: auto to center the element horizontally within it's column. The element takes up a specified width and splits the remaining space equally between the left and right margins. Challenge number

Challenge Number 3
@gprocell927
gprocell927 / m1-goals.md
Created August 15, 2016 21:59
FEE - Mod 1 Goals

GOOOOOOOOOOOALS!!!

  1. Tackle object relationship issues (in programming). Beat this into the ground and own it.

  2. Seek help early and often. Structure my pairing sessions.

  3. drill. Drill. DRILL.

  4. Just do the thing, don't dilly-dally around starting the project -- JUST START IT/ "do the damn thang".

Module 1 Week 2 Diagnostic

This exercise is intended to help you assess your progress with the concepts and techniques we've covered during the week.

When complete, fill out this form.

For these questions, write a short snippet of code that meets the requirement. In cases where the question mentions a "given" data value, use the variable given to refer to it (instead of re-writing

@gprocell927
gprocell927 / gp-prework.md
Last active June 26, 2016 20:24 — forked from mbburch/prework.md
An example template for your Turing pre-work Gist

Turing School Prework - Gabrielle Procell

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: