fearphage

$.whenAll is an extension to jQuery's $.when. The main difference is $.when stops when it receives the first rejected promise. This extension treats all successes and failures as progress events. After all the promises have completed, the global promise is resolved if there were no errors. Otherwise the global promise is rejected.

Sameple #1

$.whenAll($.get('http://github.com'), $.get('good luck with this one'))
  .then(
    // success callback
    function(request) {}
    // failure callback - called once at the end
 ,function() {}

fearphage

Archidekt Enhancements

Current Functionality

Quick Add

1. Enter selects the first element in the dropdown.
2. Ctrl-Enter adds the selected card to the maybeboard.
3. Shift-Enter adds the selected card to the sideboard.

fearphage

The goal is to add N new elements to the DOM as quickly and as painlessly as possible.

I have access to jQuery and found the code below to be faster than the following:

$(parentElement)
  .append(Array(1001).join(template))
;

fearphage

Original source of self-propagating Facebook worm

Original location: http://pelorak.info/verify.js

fearphage

#!/bin/bash

# Requirements: dialog mpv
# Optional: youtube-dl wget hq
# Arguments: none
#
# Changelog:
# > + from function to standalone script
#   + menu stack for saving previous menu command
#   + choices stack for saving previous menu choice

fearphage

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "your_email@youremail.com"

fearphage

# Python/Django files
*.pot
*.py[cod]

# Folder view configuration files
.DS_Store
Desktop.ini

# Thumbnail cache files
._*

fearphage

az-get

Returns a property value of a resource passing additional params as needed.

Usage

az-get <resource> <property> [additional params]

fearphage

#!/usr/bin/env bash

mapfile -t meh < <(ps -ax)

echo "found ${#meh[@]} processes"

fearphage

#System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

##Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?