jamesgary

Incremental Design

Rebecca Miller-Webster and Savannah Wolf

• Rebecca: Developer, Savannah: Designer

• How do you make design changes?

• Big redesigns are often long and frustrating

• Designers throw the design over the wall

• Developers either are confused by it, or 'screw it up'

• Redesigning page by page can lead to technical debt, and is awkward

jamesgary

Object-Oriented Lessons for a Service-Oriented World

Chris Kelly (@amateurhuman)

• Works for New Relic as Happiness Engineer
• These aren't hard principles, mostly ideas for now
• Monorail - Monolithic Rails App
• Network-based application software instead of SOA
• (not necessarily building 'service')
• Monorail (which is a mess) <-> Cache <-> Database
• Your app is a special snowflake that breaks every time something changes.
• Apt metaphor: Crystaline architecture shatters when a small thing changes

jamesgary

Testing HTTP APIs in Ruby

@shaiguitar

• Everything as a service
• Test it!
• Problem statement: Testing a server/client HTTP API
• Good plan:
  • Create API
  • Build client lib that can be used in confusmer apps
• Make it easy for consumer apps to test w/ our client library

jamesgary

#!/usr/bin/env ruby
 
require 'rubygems'
require 'gmail'
 
class SecretSanta
  class << self
    def get_secret_santas(people, couples)
      invalid = true
      while(invalid) do