bds

Rules for good testing

Look at the following image...

...it shows an object being tested.

You can't see inside the object. All you can do is send it messages. This is an important point to make because we should be "testing the interface, and NOT the implementation" - doing so will allow us to change the implementation without causing our tests to break.

bds

#Install and use pip in a local directory without root/sudo access. #####By: @saurabhshri

##Why? Many users when are given server access, do not have root (or sudo) privileges and can not simply do sudo apt-get install python-pip . Here's an easy way you can install and use pip without root (or sudo) access in a local directory. Note : This works without easy_install too.

##How?

bds

tmux cheatsheet

As configured in my dotfiles.

start new:

tmux

start new with session name:

bds

puts ("2070".."2090").map {|i| [i.hex].pack("U"); }

bds

Keybase proof

I hereby claim:

• I am bds on github.
• I am bds (https://keybase.io/bds) on keybase.
• I have a public key ASB4Evif_EDD-524nYlYchAx214Pa2eHhrGmrq7u7Lt8sgo

To claim this, I am signing this object:

bds

sudo ngrep -q -T -W byline host api.zuora.com
sudo ngrep -q -T -W byline port 27017

bds

#!/usr/bin/env bash
for i in {0..255} ; do
    printf "\x1b[38;5;${i}mcolour${i}\n"
done

bds

set nocompatible " We are using Vim
syntax on

" * PLUGINS

" set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()

" let Vundle manage Vundle, required

bds

# Cult of Vi
set -o vi
export VISUAL=vim
export EDITOR="$VISUAL"

# Colors!
alias ls='ls -G'

# History
export HISTFILE=~/.bash_history

bds

set nocompatible                                      " We are using Vim
syntax on

set colorcolumn=80
set ruler

hi StatusLine   ctermfg=0  ctermbg=3 cterm=bold      " Window highlighting
hi StatusLineNC ctermfg=white ctermbg=4 cterm=none
hi Folded       ctermfg=244 ctermbg=0 cterm=none     " Code folding highlight