Erik Beeson ebeeson

## latency.markdown

      
              2 files
            
          
              747 forks
            
          
              50 comments
            
          
              4457 stars
            
          
                hellerbarde
                / latency.markdown
            
            
              Created
              May 31, 2012 13:16
                — forked from jboner/latency.txt
            
              
                Latency numbers every programmer should know
              
          
    Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

  
## clone-all-twitter-github-repos.sh
curl -s https://api.github.com/orgs/twitter/repos?per_page=200 | ruby -rubygems -e 'require "json"; JSON.load(STDIN.read).each { |repo| %x[git clone #{repo["ssh_url"]} ]}'

## how-to-set-up-stress-free-ssl-on-os-x.md

      
              8 files
            
          
              142 forks
            
          
              32 comments
            
          
              916 stars
            
          
                jed
                / how-to-set-up-stress-free-ssl-on-os-x.md
            
            
              Last active
              July 10, 2024 14:35
            
              
                How to set up stress-free SSL on an OS X development machine
              
          
    How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:


Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.


Use production SSL certificates locally. This is annoying


## background.js
// this is the background code...

// listen for our browerAction to be clicked
chrome.browserAction.onClicked.addListener(function (tab) {
	// for the current tab, inject the "inject.js" file & execute it
	chrome.tabs.executeScript(tab.ib, {
		file: 'inject.js'
	});
});

## whiteboardCleaner.md

      
              1 file
            
          
              228 forks
            
          
              56 comments
            
          
              2094 stars
            
          
                lelandbatey
                / whiteboardCleaner.md
            
            
              Last active
              June 16, 2024 13:44
            
              
                Whiteboard Picture Cleaner - Shell one-liner/script to clean up and beautify photos of whiteboards!
              
          
    Description

This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.
The script is here:
#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"

Results


## webkitmediasource-is-type-supported.html
<!DOCTYPE html>
<html>
<head>
    <script>
        window.MediaSource = window.MediaSource || window.WebKitMediaSource;

        function testTypes(types) {
            for (var i = 0; i < types.length; ++i)
                console.log("MediaSource.isTypeSupported(" + types[i] + ") : " + MediaSource.isTypeSupported(types[i]));
        }

## bs3-require-shims.js
require.config({
    paths: {
        /* other paths are omitted */
        'bootstrap': '../libs/bootstrap'
    },
    shim: {
        'bootstrap/affix':      { deps: ['jquery'], exports: '$.fn.affix' },
        'bootstrap/alert':      { deps: ['jquery'], exports: '$.fn.alert' },
        'bootstrap/button':     { deps: ['jquery'], exports: '$.fn.button' },
        'bootstrap/carousel':   { deps: ['jquery'], exports: '$.fn.carousel' },

## The Technical Interview Cheat Sheet.md

      
              1 file
            
          
              3399 forks
            
          
              904 comments
            
          
              8428 stars
            
          
                tsiege
                / The Technical Interview Cheat Sheet.md
            
            
              Last active
              August 26, 2024 00:15
            
              
                This is my technical interview cheat sheet. Feel free to fork it or do whatever you want with it. PLEASE let me know if there are any errors or if anything crucial is missing. I will add more links soon.
              
          
    ANNOUNCEMENT

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!


\

  
## npm-upgrade-bleeding.sh
#!/bin/sh

set -e
set -x

for package in $(npm -g outdated --parseable --depth=0 | cut -d: -f3)
do
    npm -g install "$package"
done

## bling.js
/* bling.js */

window.$ = document.querySelectorAll.bind(document);

Node.prototype.on = window.on = function (name, fn) {
  this.addEventListener(name, fn);
};

NodeList.prototype.__proto__ = Array.prototype;
	// this is the background code...

	// listen for our browerAction to be clicked
	chrome.browserAction.onClicked.addListener(function (tab) {
	// for the current tab, inject the "inject.js" file & execute it
	chrome.tabs.executeScript(tab.ib, {
	file: 'inject.js'
	});
	});
	<!DOCTYPE html>
	<html>
	<head>
	<script>
	window.MediaSource = window.MediaSource \|\| window.WebKitMediaSource;

	function testTypes(types) {
	for (var i = 0; i < types.length; ++i)
	console.log("MediaSource.isTypeSupported(" + types[i] + ") : " + MediaSource.isTypeSupported(types[i]));
	}
	require.config({
	paths: {
	/* other paths are omitted */
	'bootstrap': '../libs/bootstrap'
	},
	shim: {
	'bootstrap/affix': { deps: ['jquery'], exports: '$.fn.affix' },
	'bootstrap/alert': { deps: ['jquery'], exports: '$.fn.alert' },
	'bootstrap/button': { deps: ['jquery'], exports: '$.fn.button' },
	'bootstrap/carousel': { deps: ['jquery'], exports: '$.fn.carousel' },
	#!/bin/sh

	set -e
	set -x

	for package in $(npm -g outdated --parseable --depth=0 \| cut -d: -f3)
	do
	npm -g install "$package"
	done
	/* bling.js */

	window.$ = document.querySelectorAll.bind(document);

	Node.prototype.on = window.on = function (name, fn) {
	this.addEventListener(name, fn);
	};

	NodeList.prototype.__proto__ = Array.prototype;