Tamas Kalman ktamas77

Architecture in Elm

This document is a collection of concepts and strategies to make large Elm projects modular and extensible.

We will start by thinking about the structure of signals in our program. Broadly speaking, your application state should live in one big foldp. You will probably merge a bunch of input signals into a single stream of updates. This sounds a bit crazy at first, but it is in the same ballpark as Om or Facebook's Flux. There are a couple major benefits to having a centralized home for your application state:

There is a single source of truth. Traditional approaches force you to write a decent amount of custom and error prone code to synchronize state between many different stateful components. (The state of this widget needs to be synced with the application state, which needs to be synced with some other widget, etc.) By placing all of your state in one location, you eliminate an entire class of bugs in which two components get into inconsistent states. We also think yo

Commit, clone a container

To 'clone' a container, you'll have to make an image of that container first, you can do so by "committing" the container. Docker will (by default) pause all processes running in the container during commit to preserve data-consistency.

For example;

docker commit --message="Snapshot of my container" my_container my_container_snapshot:yymmdd

The Ultimate Unit Testing Cheat-sheet

Sinon Chai
Chai
Sinon

#!/usr/bin/env bash

# Assuming OS X Yosemite 10.10.4

# Install XCode and command line tools
# See https://itunes.apple.com/us/app/xcode/id497799835?mt=12#
# See https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/xcode-select.1.html
xcode-select --install

Debug your PHP in Docker with Intellij/PHPStorm and Xdebug

For your local dev, create a Dockerfile that is based on your production image and simply install xdebug into it. Exemple:

FROM php:5

RUN yes | pecl install xdebug \
&amp;&amp; echo "zend_extension=$(find /usr/local/lib/php/extensions/ -name xdebug.so)" &gt; /usr/local/etc/php/conf.d/xdebug.ini \

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

	#!/bin/bash

	set -e

	if [ $# -eq 0 ]; then
	echo "USAGE: $0 plugin1 plugin2 ..."
	exit 1
	fi

	plugin_dir=/var/lib/jenkins/plugins

	#!/usr/bin/env php
	<?php error_reporting(E_ALL); set_time_limit(0);

	if (php_sapi_name() !== "cli" \|\| $argc < 4) {
	echo "Usage: php ", $argv[0], " [nickname] [password] [#channel]";
	exit(1);
	}

	$host = "irc.twitch.tv";
	$ip = gethostbyname($host);

	#!/bin/bash

	#New Relic API Key see https://docs.newrelic.com/docs/apis/rest-api-v2/requirements/api-key#creating
	NR_API_KEY="INSERT_API_KEY_HERE"

	#Find New Relic App Name, if your top level folder is not the name of your application change the below two lines to simply NR_APP_NAME="MY_APP_NAME".
	NR_APP_NAME=$(git rev-parse --show-toplevel)
	NR_APP_NAME=$(basename "$NR_APP_NAME")

	#Get the current git branch

	#!/bin/bash

	# update the TOKEN and the CHANNELID, rest is optional
	# you may need to connect with a websocket the first time you run the bot
	# use a library like discord.py to do so

	curl -v \
	-H "Authorization: Bot TOKEN" \
	-H "User-Agent: myBotThing (http://some.url, v0.1)" \
	-H "Content-Type: application/json" \