steinnes

# I found this somewhere on the internet and modified just slightly.
# Sorry whoever I got it from, I don't remember where so no credit for you :-(

function color_my_prompt {
    local __user_and_host="\[\033[01;32m\]\u:"
    local __cur_location="\[\033[01;34m\]\w"
    local __git_branch_color="\[\033[31m\]"
    local __git_branch='`git branch 2> /dev/null | grep -e ^* | sed -E  s/^\\\\\*\ \(.+\)$/\(\\\\\1\)\ /`'
    local __prompt_tail="\[\033[3m\]$"
    local __last_color="\[\033[00m\]"

steinnes

#!/bin/bash
CMD=$1

cmds=`bash -c "$CMD"`

while [ 0 ]; do
        new_cmds=`bash -c "$CMD"`;
        let cmds_per_sec="$new_cmds - $cmds";
        echo $cmds_per_sec;
        cmds=$new_cmds;

steinnes

#!/bin/bash
# quick little script to make an alert window popup when AWS have updated the SSL on
# a host -- can be used to monitor something else, but the best use case is obviously
# when waiting for a third party to fix something.
#
# uses https://github.com/titanous/heartbleeder/
# runs on OS X -- probably the osascript line can be replaced with a similar oneliner
# on linux

HOST=$1

steinnes

import redis
import sys

port = None
try:
    port = int(sys.argv[2])
except:
    pass
r = redis.Redis(sys.argv[1], port)

steinnes

import json
import simplejson
import ujson
import msgpack
import time

class Timer(object):
    def __init__(self, name):
        self.name = name

steinnes

"3" Golden Rules for Bug Reports

A common problem with bug reports, according to developers, is that they are often too vague to be helpful. This can frustrate both reporters and developers, and damage an otherwise productive and positive scenario.

If a report is vague, it becomes extremely hard to fix. Why? Because the developer may not be able understand what was going on (from the vague description) and is very unlikely to be able to duplicate the behavior.

Thankfully it is extremely easy to prevent this from happening -- we just need to make your sure our bug reports answer three simple questions:

1. What did I do?