worace

Purpose of Code Review

Remember that the purpose of code review is to learn from the feedback of your peers and give constructive feedback to help one another improve. Even when it's not your code being reviewed, you can often pick up a lot of ideas from the discussion. When it is your code being reviewed, keep in mind that software is neither done nor perfect -- there's always something we can do better.

Code Review Process

1. Clone the project -- project owner should make sure beforehand the project is pushed to github
2. Setup dependencies (bundle, create DBs, etc.) -- A good project README will have clear instructions for what steps are necessary.
3. Use the project (5 minutes) -- If it's a CLI try working through the commands a few times. If it's a web app, click around and try to follow a few different "user paths" through the app. Run the project. The project owner will probably need to serve as a guide here, but the goal is to quickly get a broad understanding of what the ap

mikedao

Create VPC
Create Security Group
Create incoming and outgoing rules for SSH, HTTP, Sinatra and Rackup, 443
Create Key Pair
cd ~/.ssh
mv ~/Downloads/Turing.pem .
chmod 400 Turing.pem
ssh-add -k Turing.pem
Launch Instance
ubuntu 14.04

chandracarney

##Useful packages:

• Trailing Spaces (shows if you have extra whitespace anywhere in your project. I recommend changing the highlight color from blue)
• Highlight Selected (upon double-click- shows multiples of words in file: useful when trying to see where a variable is coming from)
• Seeing is Believing (most of us have this, though)

##Useful commands in general on an Apple (these also apply in Atom):

• command + tab: switches between applications
• command + ~: switches between windows of the same application
• command + number: changes to specific tabs if you have multiples open (may not work in Safari)
• command + W: closes window/tab

wfro

Vim/tmux workshop (11/7)

Modes

• visual - select
• normal - where you can move around and modify stuff
• insert - insert text
• command - vim's command line (hit : and type things)

Rebinding esc

ivanoats

# .railsrc
-B #Skip Bundle
-T #Skip Test-Unit
-d postgresql #Use postgres

ryansobol

Originally published in June 2008

When hiring Ruby on Rails programmers, knowing the right questions to ask during an interview was a real challenge for me at first. In 30 minutes or less, it's difficult to get a solid read on a candidate's skill set without looking at code they've previously written. And in the corporate/enterprise world, I often don't have access to their previous work.

To ensure we hired competent ruby developers at my last job, I created a list of 15 ruby questions -- a ruby measuring stick if you will -- to select the cream of the crop that walked through our doors.

What to expect

Candidates will typically give you a range of responses based on their experience and personality. So it's up to you to decide the correctness of their answer.

jakeonrails

data:text/html, <style type="text/css">#e{position:absolute;top:0;right:0;bottom:0;left:0;}</style><div id="e"></div><script src="http://d1n0x3qji82z53.cloudfront.net/src-min-noconflict/ace.js" type="text/javascript" charset="utf-8"></script><script>var e=ace.edit("e");e.setTheme("ace/theme/monokai");e.getSession().setMode("ace/mode/ruby");</script>

jt

If someone forks a gist and you'd like to merge their changes. Do this:

1. clone your repo, I use the name of the gist

    git clone git://gist.github.com/1163142.git gist-1163142
   

2. add a remote for the forked gist, I'm using the name of my fellow developer

    git remote add aaron git://gist.github.com/1164196.git