dexterous

require 'rubygems'
require 'expectations'

Expectations do

expect(1){ proc { |a| a }.call(1) }
expect([1, 2]){ proc { |a| a }.call(1, 2) } #fails
expect(1){ proc { |a, b| a }.call(1, 2) }

expect(1){ Proc.new { |a| a }.call(1) }

dexterous

import boto3
import sys
import Queue
import threading

work_queue = Queue.Queue()

sqs = boto3.resource('sqs')

from_q_name = sys.argv[1]

dexterous

# CLOSURES IN RUBY     Paul Cantrell    https://innig.net
# Email: username "paul", domain name "innig.net"

# I recommend executing this file, then reading it alongside its output.
#
# Alteratively, you can give yourself an unreasonable Ruby test by deleting all
# the comments, then trying to guess the output of the code!
#
# (Naive HR departments, please do not use that idea as a hiring quiz.)

dexterous

{
  "settingsVersion": "1.67.4",
  "exclusionRules": [
    {
      "pattern": "https?://(mail|calendar|keep|photos|groups|drive|meet|chat|messages).google.com/*",
      "passKeys": ""
    },
    {
      "pattern": "https?://(mobile.)?twitter.com/*",
      "passKeys": ""

dexterous

(defn how-not-to-factorial [x]
  (condp #(< %2 %1) x
    1 (throw (IllegalArgumentException.))
    3 x
    (loop [acc (bigint x) prev (dec x)]
      (if (= prev 2) (* acc 2) (recur (* acc prev) (dec prev))))))

;; when you want to factorial...
(defn just-factorial [n] (apply * (range 1N (inc n))))

dexterous

Keybase proof

I hereby claim:

• I am dexterous on github.
• I am saagermhatretw (https://keybase.io/saagermhatretw) on keybase.
• I have a public key ASCjkQF0HpQb9GHrWxwaG1XmCcxpHtk3fBSNw49vTAPEzAo

To claim this, I am signing this object:

dexterous

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 really have SREs and they make en

dexterous

#!/bin/bash

echo "Here's what we're parsing"
cat -T input

echo ''
echo "First, we try awk and then cut"
echo ''

set -o xtrace

dexterous

(defn rotate [v n]
  (cond
    (zero? n) v
    (pos? n) (vec (concat (nthrest v n) (take n v)))
    (neg? n) (rotate v (+ (count v) n))))

dexterous

import groovyx.gpars.GParsExecutorsPool

GParsExecutorsPool.withPool(3) {
    (0..<10).eachParallel { worker ->
        try {
            println "attempting $worker"
            def connection = 'http://httpbin.org/delay/2'.toURL().openConnection().tap { it.requestMethod = 'HEAD' }
            println "$worker $connection.responseCode"
        } catch(IOException x) {
            println x