danielfarrell

Scrumban Process

Description of document

The purpose of this document is to outline the Scrumban process for use in Mobelux projects. This is a living document, and subject to change.

Overview

Some teams may choose to implement a Scrumban(Hybrid Scrum and Kanban) process on development projects. This is a good fit for new products and other projects that could have lots of changes or team availability inconsistencies.

michelsalib

@timestampable
class Dog {
    public name: string = 'Paul';
}

function timestampable(func) {
    return <any>(function() {
        var genericConstructor = () => {};
        genericConstructor.prototype = func.prototype;
        var instance = new genericConstructor();

rolaveric

{
  "definitions": {
    "nameMixin": {
      "type": "object",
      "properties": {
        "nameFirst": {"type": "string"},
        "nameLast": {"type": "string"}
      },
      "required": ["nameFirst", "nameLast"]
    },

bendc

// array utils
// =================================================================================================

const combine = (...arrays) => [].concat(...arrays);

const compact = arr => arr.filter(Boolean);

const contains = (() => Array.prototype.includes
  ? (arr, value) => arr.includes(value)
  : (arr, value) => arr.some(el => el === value)

pgilad

Instructions

• copy the file commit-msg to .git/hooks/commit-msg
• make sure your delete the sample file .git/hooks/commit-msg.sample
• Make commit msg executable. chmod +x .git/hooks/commit-msg
• Edit commit-msg to better fit your development branch, commit regex and error message
• Profit $$

Shell example

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

mattpodwysocki

// Observable to Promise
var promise = Rx.Observable.return(42).toPromise(RSVP.Promise);
promise.then(console.log.bind(console));
// => 42
 
// Using config instead of argument
Rx.config.Promise = RSVP.Promise;
var promise = Rx.Observable.return(42).toPromise();
promise.then(console.log.bind(console));
// => 42

gordonbrander

// Minimal FRP Behaviors and Events.

// An event function is any function of shape `function (next) { ... }` where
// `next(value)` is a callback to be called by event function. Transformations
// of event are accomplished by wrapping event with another event function,
// and consuming original event within (CPS).

// A behavior is any function of shape `function (time) { ... }`, where
// `time` is current time. Behaviors may capture state, return value from time,
// or be constant. Behaviors must always return a value, but value may

mwhite

The Ultimate Git Alias Setup

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bashrc

hisui

// stream.ts - A TypeScript module for FRP.
//   - https://gist.github.com/hisui/6261547
//   - tsc stream.ts -t es5 --sourcemap --noImplicitAny
module sf {

  export class Packet<T> {

    constructor(private _flags:number, private _value:any=void 0) {}

    static next<A>(e:A):Packet<A> {