Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺
Locally, I'm at this commit:
$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <[email protected]>
Date: Sun Apr 15 16:35:03 2012 +0200
When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.
| <?php | |
| /** | |
| * Make asynchronous requests to different resources as fast as possible and process the results as they are ready. | |
| */ | |
| class Requests | |
| { | |
| public $handle; | |
| public function __construct() | |
| { |
| --- | |
| layout: default | |
| title: Archives | |
| --- | |
| <h1>{{ page.title }}</h1> | |
| <div class="archives"> | |
| {% for month in page.months %} | |
| <h2>{{ month | date:"%B" }} <small>{{ month | date:"%Y" }}</small></h2> | |
| <ul> | |
| {% for post in page.posts_by_month[month] %} |
| <?php | |
| /** | |
| * Merge two dimensional arrays my way | |
| * | |
| * Will merge keys even if they are of type int | |
| * | |
| * @param array $array1 Initial array to merge. | |
| * @param array ... Variable list of arrays to recursively merge. | |
| * |
| <!doctype html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1" /> | |
| <title>Enterprisify your Java Class Names! (by Hay Kranen)</title> | |
| <style> | |
| body { | |
| background: white; | |
| text-align: center; |
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
| /* | |
| * insertAdjacentHTML.js | |
| * Cross-browser full HTMLElement.insertAdjacentHTML implementation. | |
| * | |
| * 2011-10-10 | |
| * | |
| * By Eli Grey, http://eligrey.com | |
| * Public Domain. | |
| * NO WARRANTY EXPRESSED OR IMPLIED. USE AT YOUR OWN RISK. | |
| */ |
Every so often I have to restore my gpg keys and I'm never sure how best to do it. So, I've spent some time playing around with the various ways to export/import (backup/restore) keys.
cp ~/.gnupg/pubring.gpg /path/to/backups/
cp ~/.gnupg/secring.gpg /path/to/backups/
cp ~/.gnupg/trustdb.gpg /path/to/backups/
| /* | |
| * Full example here: http://jsfiddle.net/jboesch26/3SKsL/1/ | |
| */ | |
| $.fn.outerHTML = function(){ | |
| // IE, Chrome & Safari will comply with the non-standard outerHTML, all others (FF) will have a fall-back for cloning | |
| return (!this.length) ? this : (this[0].outerHTML || ( | |
| function(el){ | |
| var div = document.createElement('div'); |
| // Global variables | |
| var word, count, time, status; // search status | |
| var running; // should status be updated? | |
| var showPause, showResume, showStop; // to show or hide buttons | |
| var worker; // main WebWorker | |
| $(document).ready(function () { | |
| // Update DOM every 500 ms | |
| setInterval("updateDom()", 500); |