Arkadius Jonczek arkadiusjonczek

Overview

Getting clients, managers, project managers, designers, and developers on the same page when it comes to feature expectations is hard. Everyone speaking the same language (literally) can go a long way to achieving the same, metaphorically.

There are three common formats that are great for written and verbal communication between stakeholders with different backgrounds, responsibilities, and risk exposures. They are each natural-language, narrative formats (they use plain english) that anyone can understand, but their structrued nature is proven to help clearly communicate behavior, specify intent and synchronize expectations.

Connextra user stories

Great for high level feature description
Typically bad for detailed behavior description

Installing SSHPASS

SSHPass is a tiny utility, which allows you to provide the ssh password without using the prompt. This will very helpful for scripting. SSHPass is not good to use in multi-user environment. If you use SSHPass on your development machine, it don't do anything evil.

Installing on Ubuntu

apt-get install sshpass

Installing on OS X

Squashing Git Commits

The easy and flexible way

This method avoids merge conflicts if you have periodically pulled master into your branch. It also gives you the opportunity to squash into more than 1 commit, or to re-arrange your code into completely different commits (e.g. if you ended up working on three different features but the commits were not consecutive).

Note: You cannot use this method if you intend to open a pull request to merge your feature branch. This method requires committing directly to master.

Switch to the master branch and make sure you are up to date:

Processing JSON using jq

jq is useful to slice, filter, map and transform structured json data.

Installing jq

On Mac OS

brew install jq

	#!/bin/bash
	# bash generate random alphanumeric string
	#

	# bash generate random 32 character alphanumeric string (upper and lowercase) and
	NEW_UUID=$(cat /dev/urandom \| tr -dc 'a-zA-Z0-9' \| fold -w 32 \| head -n 1)

	# bash generate random 32 character alphanumeric string (lowercase only)
	cat /dev/urandom \| tr -dc 'a-z0-9' \| fold -w 32 \| head -n 1

	# Idempotent way to build a /etc/hosts file with Ansible using your Ansible hosts inventory for a source.
	# Will include all hosts the playbook is run on.
	# Inspired from http://xmeblog.blogspot.com/2013/06/ansible-dynamicaly-update-etchosts.html

	- name: "Build hosts file"
	lineinfile: dest=/etc/hosts regexp='.*{{ item }}$' line="{{ hostvars[item].ansible_default_ipv4.address }} {{item}}" state=present
	when: hostvars[item].ansible_default_ipv4.address is defined
	with_items: groups['all']

	package main

	import (
	"crypto/tls"
	"crypto/x509"
	"flag"
	"io/ioutil"
	"log"
	"net/http"
	)

	# For example, run "npm install"
	docker run -v "$PWD":/usr/src/app -w /usr/src/app node:4 npm install

	# This command creates a container (downloading one first if you don't have it locally), runs the command in a current directory and quits the container
	# Great Success!

	#!/bin/bash -e

	##
	# WordPress Installation and VirtualHost Creation
	#
	# Description: Installs a WordPress website in the ~/Sites folder, creates a homepage,
	# cleans up the WP install a bit, deletes the akismet and hello dolly plugins, creates the permalinks,
	# clones the roots/sage theme framework to the theme folder, deletes all the other WP default themes,
	# installs/runs npm and bower and runs gulp to create the initial assets, adds a custom gitignore file
	# to /wp-content, installs the roots/soil plugin, creates a git repo in wp-content, saves the WordPress

	FROM postgres
	ENTRYPOINT ["/usr/bin/pg_dump"]