paulirish

Option 1: Command-line download extension as zip and extract

extension_id=jifpbeccnghkjeaalbbjmodiffmgedin   # change this ID
curl -L -o "$extension_id.zip" "https://clients2.google.com/service/update2/crx?response=redirect&os=mac&arch=x86-64&nacl_arch=x86-64&prod=chromecrx&prodchannel=stable&prodversion=44.0.2403.130&x=id%3D$extension_id%26uc" 
unzip -d "$extension_id-source" "$extension_id.zip"

Thx to crxviewer for the magic download URL.

mnot

Edward Snowden at IETF 93

Edward Snowden answered questions after a showing of CITIZENFOUR at the IETF93 meeting; this is a transcript of the video recording.

For more information, see the Internet Society article.

• Introduction
• Scale of Pervasive Monitoring
• Returning to the US
• Preserving the Internet

chrismdp

#!/bin/bash
# NOTE: requires ImageMagick
# NOTE: will tint to the Solarized Dark default background scheme, as the iTerm background blend option didn't lower the contrast enough for me
# NOTE: Optimised for a 1280x800 point screen (my 13" Retina MBP)

set -e

index=$[ 1 + $[ RANDOM % 10 ]]
img=`curl https://unsplash.com/rss/ | xmllint --xpath '/rss/channel/item['$index']/image/url/text()' -`
curl "$img" > ~/unsplash-latest.jpg &&

holman

require_relative "test_helper"

require "open-uri"
require "net/http"

class EmojiTest < Blog::Test
  def test_no_emoji
    posts.each do |post|
      content = File.read(post)
      refute_match /:[a-zA-Z0-9_]+:/, content,

rosiehoyem

#API Best Practices
##Routes
Restricting Routes											
    resources :zombies, only: [:index, :show]
    resources :humans, except: [:destroy, :edit, :update] 

##Subdomain						
Keeping our API under its own subdomain allows load balancing traffic at the DNS level. 
    resources :zombies, constraints: { subdomain: 'api' }
    resources :humans, constraints: { subdomain: 'api' }

rikukissa

.DS_Store

icholy

#!/usr/bin/env python

# Source: http://www.codingninja.co.uk/best-programmers-quotes/

quotes = [ 
  {
    "text": "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies.",
    "author": "C.A.R. Hoare, The 1980 ACM Turing Award Lecture"
  }, {
    "text": "The computing scientist's main challenge is not to get confused by the complexities of his own making.",

icholy

#!/bin/bash
#
# Author: Ilia Choly <ilia.choly@gmail.com>
# Year: 2014
# 

if [[ -z "$1" ]]; then
  echo "usage: graph_memory.sh <pid>"
  exit 1
fi

timruffles

In many production systems you'll want to have one module capable of talking to many potential implementations of a collaborator module (e.g a in memory cache, a redis-based cache etc). While testing it's useful to control which module the module under test is talking to.

Here are the approaches I can see. The two points that seem to divide the approaches are their tool-ability (dialyzer) and their ability to handle stateful implementations (which need a pid).

Passing modules

Modules are first class, so you can pass them in. Used in EEx, where passed module must implement a behaviour.

dhh

# Original Rails controller and action
class EmployeesController < ApplicationController
  def create
    @employee = Employee.new(employee_params)
    
    if @employee.save
      redirect_to @employee, notice: "Employee #{@employee.name} created"
    else
      render :new
    end