Alex Gompper alxgmpr

create tasks T{NNNN} asign them
create a branch with name like "T{NNNN}-boo-hoo"
git checkout -b T1234-boo-foo
commit changes on that branch until it gets ready to be reviewed
git commit -am 'first'
git commit -am 'now it works'
check if it's lint free (NOTE: it runs lint against only modified files)
arc lint
push a review request to the server. This will create a diff with id D{NNNN}
arc diff

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

So, I was reading Why You shouldn’t use lodash anymore and use pure JavaScript instead, because once upon a time, I shifted from Underscore to Lodash, and I'm always on the lookout for the bestest JavaScript stdlib. At the same time, there was recently an interesting conversation on Twitter about how some of React's functionality can be easily implemented in modern vanilla JS. The code that came out of that was elegant and impressive, and so I have taken that as a message to ask if we really need the framework.

Unfortunately, it didn't start out well. After copy-pasting the ~100 lines of code that Lodash executes to perform a find, there was then this shocking claim: .

	function keepTrying(otherArgs, promise) {
	promise = promise\|\|new Promise();

	// try doing the important thing

	if(success) {
	promise.resolve(result);
	} else {
	setTimeout(function() {
	keepTrying(otherArgs, promise);

	import requests
	import json
	import sys
	import argparse


	_strip = ['http://', 'https://', 'www']

	G = '\033[92m'
	Y = '\033[93m'

	#
	# Project specific excludes
	#

	tomcat

	#
	# Default excludes
	#