Skip to content

Instantly share code, notes, and snippets.

View hmorri32's full-sized avatar
🏄‍♂️

Hugh Morrison hmorri32

🏄‍♂️
View GitHub Profile
Torch node modules: `find . -name "node_modules" -type d -prune -exec rm -rf '{}' +`
# vim:set ft=sh sw=2 sts=2:
[ -e "$SOURCE_DIR" ] || SOURCE_DIR="$HOME/hashrocket"
export SOURCE_DIR
# DEPRECATED: Use more generic SOURCE_DIR. HASHROCKET_DIR persists as a
# legacy artifact, and for 3rd-party scripts.
export HASHROCKET_DIR=$SOURCE_DIR
# Paths for prepending
@hmorri32
hmorri32 / vanilla-js-cheatsheet.md
Created January 9, 2018 15:50 — forked from thegitfather/vanilla-js-cheatsheet.md
Vanilla JavaScript Quick Reference / Cheatsheet
-- ADVANCED ACTIVE RECORD
-- RALES_ENGINE**
-- Find top 5 most expensive invoices with successful transactions
-- What do we need?
-- * invoices
-- * ID
-- * Invoice Items
-- * Quantity and unit price (multiply) (AS revenue)
-- * invoice ID
@hmorri32
hmorri32 / rebase.md
Last active November 29, 2017 02:51

Checkout a new working branch

 git checkout -b <branchname> --track

Make Changes

 git add
 git commit -m "description of changes"

Sync with remote

Setting Group Expectations

Group Member Names: EMILY WISE && HUGH MORRISON

  1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed? After school hours, no restraints, no late nights at school. Early mornings are a no go, for working collaboratively.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? In person preferably, VIA slack and or text. Lines of communication should be open most of the time. Slack works but via phone is best for urgent situations.

@hmorri32
hmorri32 / bike_share_setting_expectations.markdown
Last active October 2, 2017 22:25 — forked from Carmer/setting_expectations.markdown
Setting Expectations - Bike Share

Setting Group Expectations - Bike Share

Group Member Names: HUGH MORRISON && TIM JOO && MIGUEL SILVA

  1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed? No late nights. No weekend mornings PRE 10 AM. All other times are free. All group members are willing to put the time aside to complete the project.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? In person, via slack, via text and often. Communication preference in that order.

@hmorri32
hmorri32 / strengths_&_story_telling_reflections.md
Last active September 18, 2017 02:33
strengths_&_story_telling_reflections

Strengths & Storytelling Reflection

How have you seen yourself using these strengths at Turing? Has your understanding of these strengths changed since you first reflected on them? If so, how?

  • 1-2 paragraphs about your StrengthsFinder themes: My SF signature themes are the following : strategic. ideation. individualization. acheiver. intellection. How fantastic! According to gallup, "The Strategic theme enables you to sort through the clutter and find the best route. It is not a skill that can be taught. It is a distinct way of thinking, a special perspective on the world at large. This perspective allows you to seepatterns where others simply see complexity." Ideation asserts that "you are fascinated by ideas." Paradigm shifting stuff. Individualization claims that 'intrigued by the unique qualities of each person. You are impatient with generalizations or “types” because you don’t want to obscure what is special and distinct about each person.' As an acheiver, I feel as though "every day star
@hmorri32
hmorri32 / black_thursday_dtr
Created September 18, 2017 02:12
black_thursday_dtr
Guiding Questions to Define The Relationship:
What are your learning goals for this project? J
HUGH: I want to learn heaps about relational databases.
IZA: Learning more about CSV and databases, refining git workflow, organization, and testing.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
HUGH + IZA: I think the situation calls for different approaches. Im cool with either.
How do you communicate best? How do you appreciate receiving communication from others?
HUGH: I prefer direct communication and direct feedback. In person is better.
IZA: I communicate best in person, but also do well communicating with Slack.
How would you describe your work style?
## Module 4 Goals
* Be hired at a company in Denver, San Diego, or San Francisco
* Be at ease with es6 destructuring. Crush React/redux. Re visit Ember
* Become proficient in Node.js and express
### Strategy To Achieve Goals:
* Send outreach emails each day
* Start to tap my mentors for companies that may be able to hook it up