mbrehin

#! /bin/bash
# If you encounter any error like `declare: -A: invalid option`
# then you'll have to upgrade bash version to v4.
# For Mac OS, see http://clubmate.fi/upgrade-to-bash-4-in-mac-os-x/

# Hash using its key as a search Regex, and its value as associated error message
declare -A PATTERNS;
PATTERNS['^[<>|=]{4,}']="You've got leftover conflict markers";
PATTERNS['focus:\s*true']="You've got a focused spec";

tdd

Say, to get more comfortable before attending a 360° JS or Node.js training class.

• Codecademy’S JS class: https://www.codecademy.com/learn/javascript

• MDN’s JavaScript guide: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide

• Eloquent JavaScript, chapters 1 through 10: http://eloquentjavascript.net/

tdd

Learning

• ES6 Katas - Small, byte-size exercises to discover most aspects of ES6 features by doing interactive, online exercises. Pretty awesome.
• Learn ES2015 - A great part of Babel's website that takes you through examples of all supported ES6+ features
• ES6-Features.org - Nice ES6 / ES5 comparisons of many ES6 language features
• ES6 Features - A single-page tour of code examples for just about every ES6 feature, by Luke Hoban

Exploring in-depth

• ES6 In Depth - A great series of articles on Mozilla Developer Network (MDN); also available in French through great translation efforts.

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

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

Par exemple pour être à l'aise avant un JS Total ou un Node.js.

On parle ici du langage pur dans ses versions « traditionnelles » (ES3/ES5).

• Le cours JavaScript de Codecademy (hors "Objects I/II") : http://www.codecademy.com/fr/tracks/javascript

• Le guide JavaScript du MDN : https://developer.mozilla.org/fr/docs/JavaScript/Guide

tdd

"ensure_newline_at_eof_on_save": true,
"tab_size": 2,
"translate_tabs_to_spaces": true,
"trim_trailing_white_space_on_save": true,

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

# Put this in your ~/.gitconfig or ~/.config/git/config
# Windows users: "~" is your profile's home directory, e.g. C:\Users\<YourName>
[user]
  name = Your Full Name
  email = [email protected]
[color]
  # Enable colors in color-supporting terminals
  ui = auto
[alias]
  # List available aliases