Skip to content

Instantly share code, notes, and snippets.

View kheppenstall's full-sized avatar

Kyle Heppenstall kheppenstall

View GitHub Profile
@kheppenstall
kheppenstall / kh_prework.md
Last active September 28, 2016 20:25 — forked from mbburch/prework.md
An example template for your Turing pre-work Gist

Turing School Prework Kyle Heppenstall

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:

@kheppenstall
kheppenstall / solo_lightning_talk_outline
Created October 20, 2016 17:18
Outline for a lightning talk on the benefits of solos
Background
Mission of Colorado Outward Bound
My role
Purpose of the talk - discuss the merits of one small aspect of an Outward Bound course
Ways that the mission is achieved
Living outside for 3 weeks
Mountaineering
Walking
Rock climbing
@kheppenstall
kheppenstall / w4.md
Last active October 27, 2016 15:25 — forked from mikedao/w4.md

Module 1 Week 4 Diagnostic

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

For these questions, write a short description or 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 the information).

@kheppenstall
kheppenstall / heppenstall_black_thursday_retro.txt
Last active November 10, 2016 20:34
Black Thursday Project Retro
1. What was a opportunity for improvement in your group?
Molly and I started off not too well but progressed over the course of the project. Our main opportunity for improvement was starting the project on the same page during the first week. I took off way too fast on the project, and as a result Molly felt behind and stressed our during the first week. It may have been wise to start off coding on an exercism or something else so we familiarized each other with our different strengths / weaknesses with ruby. Luckily we slowed down a bit and ended up on the same page during the second week. Once we were on the same page with work style and speed then we were much more productive together and both people learned more.
2. What was your role?
I kept the big picture in mind during the project and held the vision / task schedule. I often initiated the tasks that we completed together. I also focused more on the analysis parts of the project than the molly since I enjoyed doing the math / calculations.
3. What
@kheppenstall
kheppenstall / dtr_expectations.markdown
Last active December 2, 2016 16:39 — forked from case-eee/dtr_expectations.markdown
Group Work Expectations

Group Expectations

Group Member Names: Josh, Drew, Kyle

Project Manager: Kyle

Defining the Relationship (DTR) Questions:

  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?
@kheppenstall
kheppenstall / new_rails.md
Last active January 9, 2017 15:49
New Rails Project

How to start a new project

ActiveRecord with RSpec

rails new my_project -T --database=postgresql --skip-turbolinks --skip-spring

group :development, :test do
  gem 'rspec-rails', '~> 3.5'
@kheppenstall
kheppenstall / project_management.md
Last active January 8, 2017 20:03
Project Management Strategies

In both Bike Share and Little Shop my team used Waffle as a project management tool. In Bike Share I was the project manager from my team. Our workflow was effective using Waffle and Github but unfortunately I was the only person managing cards. In Little Shop I shared that with my team and we were all diligent in moving cards and tagging the cards with in our pull requests to better marry Github and Waffle.

One piece of feedback from Bike Share was that pull requests were getting merged too quickly without all team members having the opportunity to review. As a result during Little Shop all pull requests were tagged with the number of reviewers needed. For small items like styling the author would recommend one review but for larger features and signficant routing / ruby the pull request would be tagged as needing all team members to review. Furthermore, we dug into the Github review feature to do a line-by-line review of code - specifying what we liked about the code and giving suggestions. Then the author

@kheppenstall
kheppenstall / flower.md
Last active January 25, 2017 17:00
Flower Exercise

Flower Exercise

My Favorite People To Work With

  • People that like to investigate and solve problems.
  • People that like are mechanical or athletic.
  • People that put a focus on learning.
  • People that take initiative.
  • People that can work collaboratively and independently.
@kheppenstall
kheppenstall / project_proposal.md
Last active February 14, 2017 23:25
Kyle and Nick E Personal Project Description

TrailSourcing

Pitch

This is an application that gives trail users and trail maintainers one platform on which to log and prioritize trail work requests/issues.

Problem

We're trying to crowdsource identifying and prioritizing trailwork. Right now trail users do not have an easy way to communicate trailwork requests or 'upvote' trailwork requests in the works. People often complain about the state of trails but do not do anything to communicate concerns or work on the trails themselves. Part of the reason is also that it is often very cumbersome to submit a trail work request or report on an issue.

@kheppenstall
kheppenstall / job_search_action_plan.md
Last active February 21, 2017 20:42
Job Search Action Plan

Kyle Heppenstall Module 4 Action Plan

Module 4 Goals

  • Job offer by last day of module 4
  • 3 interviews in module
  • 1 coffee meeting per week
  • 5 cold or warm outreach emails per week (associated with job application or not)

Strategy To Achieve Goals: