sowenjub

#!/bin/bash

# This script does the following:
# 1/ capture and download the latest backup
# 2/ load it to your local database
# 3/ run your app and open Safari

# Just replace any uppercase string with your own data

#

watson

# app/models/ability.rb

# All front end users are authorized using this class
class Ability
  include CanCan::Ability

  def initialize(user)
    user ||= User.new

    can :read, :all

rgreenjr

-- show running queries (pre 9.2)
SELECT procpid, age(clock_timestamp(), query_start), usename, current_query 
FROM pg_stat_activity 
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' 
ORDER BY query_start desc;

-- show running queries (9.2)
SELECT pid, age(clock_timestamp(), query_start), usename, query 
FROM pg_stat_activity 
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' 

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

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?

naoyamakino

RailsConf: documentation tips

• people don't read on the web
• how users read on the web http://www.nngroup.com/articles/how-users-read-on-the-web/
• F shaped pattern (Jakob Nielsen)
• what readers look at
  • menaningful text and images
  • the begining of paragraphs
  • bullet lists
  • variations in typeface

naoyamakino

How Shopify Scales Rails John Duff

The Stack:

• ruby1.9.3-p327
• rails3.2
• unicorn 4.5
• percona Mysql5.5
• memcache14.14
• redis2.6

33 app servers, 1172 unicorn workers, 5 job servers, 370 job workers

naoyamakino

1. never use a metaphor, simile, or other figure of speech which you are used to seeing in print.
2. never use a long word where a short one will do
3. if it's possible to cut a word out, always cut it out.
4. never use the passive where you can use the active
5. never use a foreign phrase, a scientific word, or a jargon word if you can think of an everday English equivalent
6. break any of these rules sooner than say anything outright barbarrous

#Five guiding principles

1. minimalism
2. get out of the way

hopsoft

# lib/tasks/db.rake
namespace :db do

  desc "Dumps the database to db/APP_NAME.dump"
  task :dump => :environment do
    cmd = nil
    with_config do |app, host, db, user|
      cmd = "pg_dump --host #{host} --username #{user} --verbose --clean --no-owner --no-acl --format=c #{db} > #{Rails.root}/db/#{app}.dump"
    end
    puts cmd

david206

Data from [https://snowflake.medium.com/]

Engineering growth: tracks

Table of Contents

• Mobile
  • Works effectively within established iOS or Android architectures, following current best practices
  • Develops new instances of existing architecture, or minor improvements to existing architecture
• Designs major new features and demonstrates a nuanced understanding of mobile platform constraints