cghiban

import random, subprocess, time

words = [
    'safe', 'wake', 'late', 'grade','cage',
    'plane', 'shape', 'away', 'gray', 'pray'
]

for i in range(len(words)):
    word = words[i]

cghiban

 # Go parameters
    GOCMD=go
    GOBUILD=$(GOCMD) build
    GOCLEAN=$(GOCMD) clean
    GOTEST=$(GOCMD) test
    GOGET=$(GOCMD) get
    BINARY_NAME=mybinary
    BINARY_UNIX=$(BINARY_NAME)_unix
    
    all: test build

cghiban

package main

import (
	"bytes"
	"encoding/json"
	"io/ioutil"
	"log"
	"net/http"
)

cghiban

use IO::Compress::Gzip qw(gzip $GzipError);
use IO::Uncompress::Gunzip qw(gunzip $GunzipError);

use Storable qw(nfreeze thaw);
use IO::Scalar ();

my $input = "ABC" x 200 . "A" x 2000;
my $output = "";
my $gh = IO::Scalar->new(\$output);
print length($input), $/;

cghiban

# python 2
# pip instal --user pykml
from pykml import parser

# kml source: https://www.census.gov/geo/maps-data/data/kml/kml_zcta.html
kml_file = 'cb_2017_us_zcta510_500k.kml'

# zip codes in one column text file
zip_file = 'our-zipcodes.txt'

cghiban

#!/bin/sh

# This pre-commit hook will prevent you from committing any line (or filename) containing
# the string NOCOMMIT. Use that tag in comments around source code you want to avoid
# accidentally committing, like temporary IP addresses or debug printfs.
#
# To add it to an existing repository, save it to .git/hooks/pre-commit (or append, if
# that file already exists). Remember to make executable (chmod +x ...)
#
# To automatically add this pre-commit hook to every repository you create or clone:

cghiban

#!/bin/bash

# usage:
#   $ echo 1234567|./nicenumber.sh
#   1,234,567
#   $ find .|wc -l|./nicenumber.sh
#   426,704

while read line; do
# run the number thru the comma mill

cghiban

import datetime
import email
import sys
import imaplib


m = imaplib.IMAP4_SSL("email.domain.com", 993)
try:
    m.login("user","abcxyz")
except Exception, e:

cghiban

Basic Workflow

Description

Different uses of git will have a different optimal workflow. This document describes a git workflow with the following characteristics:

• It is a centralized workflow, meaning multiple developers all push to a shared repository. (As opposed to a fork-and-pull-request Github-style workflow.)
• It is safe to use when collaborating on a feature branch with others, but requires no workflow changes when working alone. (So there's only one set of steps to remember.)
• Some git users rely heavily on rebases, using them for any and all conflicts. This is an unhealthy coping mechanism born of past git merge trauma. This workflow relies heavily on merges, using rebase only when it is safe to do so (with commits that have yet to be pushed).
• push --force is never needed (and may be disallowed by the remote repository.)

cghiban

#/bin/sh

input=$1

fname=$(echo $input|sed -e 's/\.mp4//')
ffmpeg -v quiet -i $input -vframes 1 -an -f image2 -y $fname.jpg