jamesgary

App = Ember.Application.create();

App.IndexRoute = Ember.Route.extend({
  model: function() {
    return EmberFire.Array.create({
      ref: new Firebase("https://dp-ember-chat.firebaseio.com/")
    });
  }
});

jamesgary

module AwesomeResource
  attr_reader :awesome_attributes

  def initialize(attributes={})
    @awesome_attributes = attributes
    @awesome_attributes.keys.each do |method_name|
      create_method(method_name.to_sym) do
        @awesome_attributes[method_name]
      end

jamesgary

Dissecting Ruby with Ruby

Richard Schneeman (@schneems)

• Get into a library
  • bundle open wicked
  • Make sure you've set your $EDITOR
• Forget fancy debuggers
  • All you need is puts
  • A rubyist's tracer round: puts "================="
• Notation

jamesgary

How to Talk to Developers

Ben Orenstein (@r00k)

Obey Law of Demeter

• Reduces coupling
• Enables refactoring

Throw something weird at people to keep their attention. Bored people don't learn anything, so focus on entertainment over being informative.

Write like a newspaper

jamesgary

What Ruby developers can learn from Go

Lionel Barrow @lionelbarrow

• Go is compiled, garbage collected, strongly typed, OO
• Lower level than Ruby, but still aimed at web
• Go has an agenda
  • Not welcome to a lot of styles of writing code
  • Prodded to write code in a certain way
  • Ruby doesn't have an agenda, but it does have idioms
• What are the design goals here?

jamesgary

From Rails to the web server to client to browser

David Padilla @dabit

• Life of a request
  • Browser creates request
  • Sends it to webserver (Unicorn)
  • Sends it to Rails
  • Sends it to spaghetti code
  • HTML is returned
• Rack's job is to communicate between webservers and frameworks

jamesgary

The Magic Tricks of Testing

Sandi Metz

• Many people say "I hate my tests"
• They kill your productivity when they're slow
• A little change can break your tests (even if they shouldn't)
• They're expensive
• They are misery incarnate
• Just delete some tests
• You may have too many tests testing the wrong tests

jamesgary

Rails vs. The Client

Noel Rappin (@noelrap)

• Problem: Want users to have "rich client exp" (even though clients don't know what that means)
• @dhh and @wycats offer different opinions (document vs json api)
• But @noelrap just wants to write an e-commerce site
• We tend to split stuff up into client stuff and server stuff between the user and data
• @dhh says that the focus is on the server. The app lives on the server
• @wycats says that the client is the focus, and the server just does whatever the client can't do (i.e. validation, persistence)
• Where does the heart of your application live?

jamesgary

Michael Lopp Keynote @rands

Stables and Volatiles

• Humans are bad at making decisions (see eletrical outlets)

• Why no one single plug?

• Look at Apple's plugs

• You're in a hurry

• Your gig has an expiration date

• Switch jobs about every 3 years

jamesgary

Humanity on Rails

Daniel Azuma

• What is 'living'?
• RailsBridge: Org to increase diversity in tech
• Diversity's a big issue
• How do we attract more minorities?
• Yahoo recently canned their remote working program
• What do we make of all of this?
• Daniel got laid off, went back to school to study theology at Regent