tdd

# STEP 1: ENSURE COMPLETION AND PROMPT FUNCTION ARE LOADED
# ========================================================

# OPTION 1: If on OSX using Homebrew:
#
# source $(brew --prefix)/etc/bash_completion.d/git-prompt.sh
# source $(brew --prefix)/etc/bash_completion.d/git-completion.bash

# OPTION 2: If on OSX using built-in Git (also works on ZSH):
#

tdd

Angular: Just say no

A collection of articles by AngularJS veterans, sometimes even core committers, that explain in detail what's wrong with Angular 1.x, how Angular 2 isn't the future, and why you should avoid the entire thing at all costs unless you want to spend the next few years in hell.

Reason for this: I'm getting tired of having to explain to everyone, chief of which all the indiscriminate Google Kool-Aid™ drinkers, why I have never believed in Angular, why I think it'll publicly fail pretty soon now (a couple years), and why it's a dead end IMO. This gist serves as a quick target I can point people to in order not to have to parrot / compile the core of the articles below everytime. Their compounded reading pretty much captures 99% of my view on the topic.

This page is accessible through http://bit.ly/angular-just-say-no and http://bit.ly/angularjustsayno, btw.

• I won't be using Angular for my next project...and neither should you. • Robe

tdd

Sections:

• g11n
• Infrastructure upgrades
• Workshop fixes
• Enhancements (mostly new workshops)
• Bootstrapping workshops and translations

tdd

function add(a, b, c) {
  return a + b + c;
}

function partial(fx) {
  var initial = Array.prototype.slice.call(arguments, 1);
  return function() {
    var args = Array.prototype.slice.call(arguments);
    return fx.apply(this, initial.concat(args));
  };

tdd

// Configuration globale au projet de JSHint
// =========================================
//
// (Y compris celui intégré à votre EDI/éditeur, normalement)
//
// [Liste complète des options possibles](http://www.jshint.com/docs/options/)

{
  // Options de restriction
  // ----------------------

tdd

var items;

// insertAt //////////////////////////////////

function insertAt(arr, pos, item) {

}

items = ['one', 'two', 'three'];
console.assert(insertAt(items, 1, 'yo') === 4);

tdd

userSchema.statics.findOrCreateByAuth = function findOrCreateByAuth(id, name, provider, done) {
  var User = this;
  User.update(
    { _id: id, provider: provider },
    { name: name, provider: provider },
    { upsert: true },
    function(err, numAffected, details) {
      if (err) {
        return done(err);
      }

tdd

Lisez plutôt…

cet article détaillé que j'ai écrit ensuite…

Je laisse le Gist ici pour ne pas casser vos liens, mais bon 😄

Par e-mailing/RSS/etc.

Chaque jour ou chaque semaine :

tdd

Workbench

We extract our test repos from this small Zip file.

• main is a "container" repository with its working copy,
• plugin is a "shared" repository with its working copy,
• remotes emulates remote bare repos for both, to better resemble regular usage.

The idea is to use plugin as a subtree of main in a vendor/plugins/demo path, and allow maintenance both ways:

tdd

export PS1='\[\e[0;36m\][\A] \u@\h:\[\e[0m\e[0;32m\]\W\[\e[1;33m\]$(__git_ps1 " (%s)")\[\e[0;37m\] \$\[\e[0m\]'