alexellis

Convert sequence of JPEG images to MP4 video

ffmpeg -r 24 -pattern_type glob -i '*.JPG' -i DSC_%04d.JPG -s hd1080 -vcodec libx264 timelapse.mp4

• -r 24 - output frame rate
• -pattern_type glob -i '*.JPG' - all JPG files in the current directory
• -i DSC_%04d.JPG - e.g. DSC_0397.JPG
• -s hd1080 - 1920x1080 resolution

Slower, better quality

ranman

talentdeficit

[#{attributes => [#{name => genus,value => <<"Steam">>},
    #{name => identifier,value => <<"q6O2/V0YbSjgb/lxNcrefw==">>},
    #{name => pokeid,value => <<"721">>},
    #{name => type,value => <<"fire">>},
    #{name => type,value => <<"water">>}],
   identity => #{name => name,value => <<"Volcanion">>}},
 #{attributes => [#{name => genus,value => <<"Mischief">>},
    #{name => identifier,value => <<"Xywiy0pTgK98p1YipkJpFw==">>},
    #{name => pokeid,value => <<"720">>},
    #{name => type,value => <<"ghost">>},

ethers

/*
In Ethereum, a contract can be written so that it returns a value for eth_call.
A Dapp can then check for success or error value of eth_call, before calling eth_sendTransaction,
to take advantage of eth_call effectively being a "preview" of the code flow that the transaction
will take.  In traditional client-server, clients can't ask servers beforehand what's going to
happen when the client makes a call; with Dapps contracts can be written so that clients can ask
for a "preview" of what is going to happen, before any funds/ethers are actually utilized
(eth_call does not cost any ethers).

Note: it is possible that in between eth_call and when eth_sendTransaction is actually mined,

frozeman

// -> Soldity
// **********

// Your Soldity contract
event Created(bytes32 indexed identifier);

contract MyContract {
    function MyContract(bytes32 identifier) {
        Created(identifier);
    }

acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

phybros

#!/bin/bash

# (optional) You might need to set your PATH variable at the top here
# depending on how you run this script
#PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

# Hosted Zone ID e.g. BJBK35SKMM9OE
ZONEID="enter zone id here"

# The CNAME you want to update e.g. hello.example.com

KonradIT

DEPRECATED:

New repo: https://github.com/konradit/gopro-linux

ck-on

<?php
/*
OCP - Opcache Control Panel   (aka Zend Optimizer+ Control Panel for PHP)
Author: _ck_   (with contributions by GK, stasilok)
Version: 0.1.7
Free for any kind of use or modification, I am not responsible for anything, please share your improvements

* revision history
0.1.7  2015-09-01  regex fix for PHP7 phpinfo
0.1.6  2013-04-12  moved meta to footer so graphs can be higher and reduce clutter

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real