manchuck

use Zend\Db\Adapter\Adapter;
use Zend\Db\TableGateway\TableGateway;
use Zend\ServiceManager\AbstractFactoryInterface;
use Zend\ServiceManager\ServiceLocatorInterface;

/**
 * Class AbstractTableFactory
 *
 * Creates a default table gateway based off the requested name

manchuck

export CLICOLOR=1
export TERM=xterm-256color

function cd() {
  builtin cd "$@";
  shopt -s nocasematch
  if [[ "$PWD" == *"/Users/adamwalzer/Sites/cmwn-games-artifact"* ]]
  then
    echo -e "\033]50;SetProfile=Dev\a"
  elif [[ "$PWD" == *"/Users/adamwalzer/Sites/cmwn-games-prod"* ]]

manchuck

• Legand of Zelda Theme
• Super Mario
• "The Devil Went Down to Georgia" - Charlie Daniels
• "Waiting for the End" - Linkin Park
• "I Believe in a Think Called Love" - The Darkness
• "Under Pressure" - Daive Bowie / Queen
• "Into the Mystic" - Van Morrison
• "Teenage Dirtbag" - Wheatus
• "Dr Worm" - They Might Be Giants
• "Birdhouse In Your Soul" - They Might Be Giants

manchuck

// Generated on 2013-12-20 using generator-angular 0.6.0
'use strict';

// # Globbing
// for performance reasons we're only matching one level down:
// 'test/spec/{,**/}*.js'
// use this if you want to recursively match all subfolders:
// 'test/spec/**/*.js'

module.exports = function(grunt) {

manchuck

Code Style Guide

1. Follow PSR 0, 1, 2
2. For gateways, use fetch, fetchBy, save, attach, detach and delete ex: fetchByEmail, saveChannel, deleteProduct, attachUser
   1. Fetch MUST include the noun on singular and All with fetching multiple ex: fetchProduct, fetchAllAccounts, fetchAllActiveUsers
   2. FetchBy MUST include the noun ex: fetchByEmail, fetchByName
   3. Save, delete, attach and detach MUST include the noun ex: attachUser, saveJob, detachAccount
   4. If you need to update part of an document, use the term update and the singular noun Good: updateUserPassword, updateProductPrice

manchuck

<?php
include 'vendor/autoload.php';

class FileObject {
    public function readBytes() { /* ... */}
}

$stub = \Mockery::mock('FileObject');

$stub->shouldReceive('readBytes')

manchuck

coverage_clover: build/logs/clover.xml
src_dir: src
service_name: travis-pro
repo_token: *********************

manchuck

My name is **** and I am the CEO at ****. ****, our team and myself are all very disappointed by your choice to discontinue our relationship.

Since day 1 we could sense a struggle with your lead developer, Chuck, to come to terms with your choice of hiring **** (and for that matter anybody else but him). There were constant comments throughout this initial period on how this was only a trial. But at the end of the day, we removed all of Gregg's fears i.e. **** did not understand your business case or were slow. We had a call with Gregg on Friday (Chuck did not show up even after confirmation). These are recorded conversations that we do for note taking purposes (only) in which Gregg makes positive comments about our work. So from a business standpoint we were as fast as anyone else and we did accomplish the targets. Remember Gregg is not at all technical and admiteddly had no clue about the 'code quality'. He was satisfied in terms of business outcome and progress. Despite that, he chose to let Chuck make a

manchuck

#!/bin/sh
echo 
exec powershell.exe -ExecutionPolicy RemoteSigned -File '.\.git\hooks\pre-commit-hook.ps1'
exit

manchuck

New Dynamx Deployment Procedure

This document described the deployment procedure for New Dynamx.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.