Skip to content

Instantly share code, notes, and snippets.

View zackforbing's full-sized avatar

Zack Forbing zackforbing

View GitHub Profile
Length Points Week
20 minutes 10 Week 2

The Concept of Require - Research

When you start working with WebPack for GameTime, you'll notice that you can't just define a variable in one file and find it in another as easily as you can in Rails.

Deliverable

Length Points Week
1 to 6 hours 25 Week 2

Exercism Comparisons

By now you are probably starting to get the feeling of Okay I can get things to work in JavaScript but how to do I get my code to not look like a horrible dumpster fire?!?

The best way to start getting a feeling for how code is written in other languages is by seeing how other people code, and comparing their style to your own critically.

Length Points Week
15 minutes 5 Week 1

ES6 Research

Throughout the module (and your journey to Google enlightenment while working on IdeaBox2.0) you may notice a few different ways that JavaScript code is being written.

That might have something to do with something called ES6 and ES5

@zackforbing
zackforbing / setting_expectations.markdown
Last active July 6, 2016 14:55 — forked from Carmer/setting_expectations.markdown
Setting Expectations for Rush Hour

Setting Group Expectations for Rush Hour

Group Member Names: Zack Forbing, Garrett Smestad, Pat Wentz

  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?

It seems like we will all be able to work as late as necessary and as early as necessary. the only conflict was tonight Garrett had to leave so we are all brushing up on ActiveRecord.

  1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?

Project workflow: WHY:

  1. Load/Reload waffle.
  2. Choose a card from the backlog in waffle. If we're working separately, it's best to move that card that you've chosen into ready and perhaps assign it to yourself as well.
  3. git checkout master
  4. git pull origin master
  5. run rspec
  6. Checkout a new branch and tag it with #issue_number
  7. Write the feature test associated with your waffle card.
  8. Run rspec, and make sure that there are no errors that blow up the stack (missing ends, forgetting capitalization, etc.)
  9. commit your feature test
@zackforbing
zackforbing / week_3.markdown
Last active May 26, 2016 17:22 — forked from worace/week_3.markdown
Module 1 Week 3 Diagnostic

Module 1 Week 3 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 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).

@zackforbing
zackforbing / zfprework.md
Last active May 7, 2016 21:49 — forked from mbburch/prework.md
Zack Forbing's Prework Gist

Zack Forbing's 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: done!