technoweenie

machine github.com
login technoweenie
password SECRET

machine api.github.com
login technoweenie
password SECRET

jcromartie

#!/usr/bin/env ruby
# -*- coding: utf-8 -*-

# prints a sparkline in the terminal using the supplied list of numbers
# examples:
#   spark.rb 10 20 30 100 90 80
#   spark.rb 1 2 0.4 0.1 1.3 0.7

@ticks = %w[▁ ▂ ▃ ▄ ▅ ▆ ▇]
values = ARGV.map { |x| x.to_f }

tbranyen

/*!
 * backbone.collectioncache.js v0.0.2
 * Copyright 2012, Tim Branyen (@tbranyen)
 * backbone.collectioncache.js may be freely distributed under the MIT license.
 */
(function(window) {

"use strict";

// Dependencies

ctalkington

source :rubygems
gem "puma"
gem "sinatra"

desandro

I'm having trouble understanding the benefit of require.js. Can you help me out? I imagine other developers have a similar interest.

From Require.js - Why AMD:

The AMD format comes from wanting a module format that was better than today's "write a bunch of script tags with implicit dependencies that you have to manually order"

I don't quite understand why this methodology is so bad. The difficult part is that you have to manually order dependencies. But the benefit is that you don't have an additional layer of abstraction.

---

magicznyleszek

Jekyll & Liquid Cheatsheet

A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.

Running

Running a local server for testing purposes:

mbbx6spp

Gerrit vs Github: for code review and codebase management

Sure, Github wins on the UI. Hands down. But, despite my initial annoyance with Gerrit when I first started using it almost a year ago, I am now a convert. Fully. Let me tell you why.

Note: This is an opinionated (on purpose) piece. I assume your preferences are like mine on certain ideas, such as:

• Fast-forward submits to the target branch are better than allowing merge commits to the target branch. The reason I personally prefer this is that, even if a non-conflicting merge to the target branch is possible, the fact that the review/pull request is not up to date with the latest on the target branch means feature branch test suite runs in the CI pipeline reporting on the review/PR may not be accurate. Another minor point is that forced merge commits are annoying as fuck (opinion) and clutter up Git log histories unnecessarily and I prefer clean histories.
• Atomic/related changes all in one commit is something worth striving for. Having your dev

cloudbring

Phoenix Ecosystem June 2015

j.mp/phoenix_ecosystem_June2015

Goal of this Document / Gist is to layout the resources and challenges to writing a complete modern web app with Phoenix and Elixir as the state of the projects are starting on June 2015

• [Why Phoenix and not Rails or Node.js?](#Why Phoenix and not Rails or Node.js?)
• Main Resources
• Common Application Requirements
• Authentication

chrismcg

/* global require, module */

var EmberApp = require('ember-cli/lib/broccoli/ember-app');
var ES6Modules = require('broccoli-es6modules');
var esTranspiler = require('broccoli-babel-transpiler');
var mergeTrees = require('broccoli-merge-trees');

var app = new EmberApp();

// Use `app.import` to add additional libraries to the generated

jeffweiss

:application.ensure_all_started(:ssl)

{:ok, handle} = :eldap.open(['ldap.example.com'], [{:port, 636}, {:ssl, true}])

authenticated = 
  :ok == :eldap.simple_bind(handle, 
    'uid=jeff,ou=users,dc=example,dc=com', 
    'notmyrealpassword')

{:ok, {:eldap_search_result, list_of_entries, _}} =