adamrdavid

gh pr list --author GH_USERNAME --state merged --limit 1000 --json url,deletions,additions --jq 'map({url, additions, deletions, net: (.additions - .deletions)}) | sort_by(.net)[:10]'

adamrdavid

adamrdavid

Database do's and don'ts

This is a generic guidline that applies mostly to Ruby on Rails and Postgres, but can be usefull for running any database migrations in CI.

Table of contents

• Table of contents
• Zero downtime migrations
  • Resources
• Basic tenets

adamrdavid

Keybase proof

I hereby claim:

• I am adamrdavid on github.
• I am adampadam (https://keybase.io/adampadam) on keybase.
• I have a public key ASDuN0n9RSS5iSrzPXuMZx4t22CJEeYEH1IgfcIEBORKiwo

To claim this, I am signing this object:

adamrdavid

var gulp = require('gulp');
var sourcemaps = require('gulp-sourcemaps');
var source = require('vinyl-source-stream');
var buffer = require('vinyl-buffer');
var browserify = require('browserify');
var watchify = require('watchify');
var babel = require('babelify');

function compile(watch) {
  var bundler = watchify(browserify('./src/index.js', { debug: true }).transform(babel));

adamrdavid

1. Your class can be no longer than 100 lines of code.
2. Your methods can be no longer than five lines of code.
3. You can pass no more than four parameters and you can’t just make it one big hash.
4. When a call comes into your Rails controller, you can only instantiate one object to do whatever it is that needs to be done. And your view can only know about one instance variable.

You can break these rules if you can talk your pair into agreeing with you.

adamrdavid

Rails Models

Generating models

$ rails g model User

Associations

belongs_to

has_one