This describes the playbook for running the Penny Game game.
Process 20 coins through system of the workers using different batch sizes.
- min 10 people
- 20 coins
(function() { | |
'use strict'; | |
angular.module('countDownLatch', []) | |
.factory('CountDownLatch', function() { | |
var service = { | |
createInstance: function(countDown, onComplete) { | |
return { | |
countDown: function() { |
import java.security.*; | |
import javax.crypto.*; | |
/** | |
* BlowfishExample.java | |
* | |
* This class creates a Blowfish key, encrypts some text, | |
* prints the ciphertext, then decrypts the text and | |
* prints that. | |
* |
/*jshint node:true */ | |
'use strict'; | |
// var pkg = require('./package.json'); | |
var buildCfg = require( './build.config.js' ); | |
var gulp = require('gulp'); | |
var del = require('del'); | |
var jshint = require('gulp-jshint'); | |
var inject = require('gulp-inject'); |
Feature branching is gaining in popularity due to the rise of Distributed Version Control Systems like Git and Mercurial. | |
Mostly because proponents of DVCSs rely on feature branching to sell DVCS. And because of the success of branching models like | |
GitFlow and GitHub Flow. | |
Like all powerful tools, there are many ways you can use DVCSs, and not all of them are good. Although the creation of feature | |
branches became very easy with DVCSs, it does not mean cheap in the long run. It comes with a certain cost which impacts the | |
stability and speed of your software delivery process. | |
During this session we will explore some of the reasons teams are using feature branches, what problems are introduced by | |
using feature branches and what techniques exist to avoid them all together. |
This describes the playbook for running the Penny Game game.
Process 20 coins through system of the workers using different batch sizes.
This describes the playbook for running the DevOps Ball Point game as shared by John Clapham on Twitter.
Pass as many balls as possible through the team into the paper cups.
NOTE: Specific examples given for options, flags, commands variations, etc., are not comprehensive.
Vim has 2 main "modes", that chance the behavior of all your keys. The default mode of Vim is Normal Mode and is mostly used for moving the cursor and navigating the current file.
Some important (or longer) commands begin with ":" and you will see the text you enter next at the bottom left of the screen.
:q[uit]
- quit (the current window of) Vim. ("Window" here is internal to Vim, not if you have multiple OS-level windows of Vim open at once.)
:q!
- force quit (if the current buffer has been changed since the last save)
:e[dit] {filename}
- read file {filename} into a new buffer.