jasonpilz

Keybase proof

I hereby claim:

• I am jasonpilz on github.
• I am jasonpilz (https://keybase.io/jasonpilz) on keybase.
• I have a public key ASBaMngx0vYo8HSc0v-9p0vgXHJd__CLd_fpX85N0EtHAQo

To claim this, I am signing this object:

jasonpilz

#!/bin/sh

# https://gist.githubusercontent.com/jasonpilz/b0e0f2c4a211220b5c575168ed08bd89/raw

# This hook runs static analysis tools before each commit. If any of the steps
# are interupted by responding with 'no' or 'n', the commit will be aborted.

# Install to existing project:
# curl -sSL https://git.io/vMt7l > .git/hooks/pre-commit; chmod +x .git/hooks/pre-commit

jasonpilz

git clone https://github.com/jasonpilz/dotfiles.git ~/.dotfiles
ln -s ~/.dotfiles/vimrc ~/.vimrc
git clone https://github.com/VundleVim/Vundle.vim.git ~/.vim/bundle/Vundle.vim
vim +PluginInstall +qall

jasonpilz

# Verify the dongle is recognized
lsusb

# Check the Kernel driver is loaded (should see 8192cu)
lsmod

# Check if wireless lan adapter(wlan0) is present
iwconfig

jasonpilz

Initial computer setup (Zsh + RVM)

Unix

My Dotfiles

mkdir ~/code_support
git clone https://github.com/jasonpilz/dotfiles ~/code_support
ln -s ~/code_support/dotfiles/vimrc ~/.vimrc
ln -s ~/code_support/dotfiles/zshrc ~/.zshrc

jasonpilz

##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)

jasonpilz

• Watch Recursion

• Answer the following questions in your fork

  Do you pronounce 'babel' in the same way?

  • Noooeee

  Follow Up Question: Will you now?

  • I sure hope so because that guy is a legend.

What is an example of why/where you might use recursion

jasonpilz

##Leap My code: here

• Responder #1 (here) - I like how Emily broke out individual methods to check each specific condtion. This would make the conditional methods more reusable.
• Responder #2 (here) - I love how this person didn't explicitly return true or false; instead the conditionals return true / false.
• Responder #3 (here) - This one is similar to the one above, but they used a ternary to return either true or false, which is not necessary.
• Responder #4 (here) - Not a fan of this solution, indentation is crazy, also hard to read the conditional flow.
• Responder #5 (here) - Interesting that this person s

jasonpilz

Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)

Step Three: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded).

Did any of the responsibilities that she lists surprise you?

• I was surprised by seeing the 'application state' category. This is not something I considered when thinking about components to test.

Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

• I would say I had clear intention of testing the 'data/server communication' category, as well as set up. I feel like the 'presentation & interaction' category would be how I would think of integration tests (I felt this video was referring only to unit tests). The 'application state' category I only considered rarley if ever.

jasonpilz

Step One: Watch Mary Rose Cook Live Codes Space Invaders from Front-Trends. (The second worst conference name ever?)

Step Two: Fork this gist.

Step Three: Respond to this question in your fork: What is one approach you can take from this Mary's code and implement in your project?

• One approach I found interesting was to have the Game object delegate the Draw() and Update() methods to the objects themself ( Player, Invader, Bullet ) Also plan to use the Keyboarder structure to nicely package the functionality of detecting keyboard input.

Step Four: Totally Optional: take a look at some of the other forks and comment if the spirit moves you.