Scott Spence spences10

Dear keyword match,

You vaguely look like someone capable of doing work.

I have a couple jobs that I'm not going to bother to describe because that would have meant I needed to take the time to look at your actual experience and see if any of them are actually a fit. But trust me, these are big time real jobs that actually exist and would be perfect for you based on the fact that you matched a keyword.

Instead of telling you more, I'm going to ask you to tell me what you are doing now. If my fishing trip is successful, then I'll take the time to look and see if you might be a fit for one of the jobs I'm recruiting for. If you are, I might get back to you.

Thanks for your time, Recruiter Dude.

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

Jekyll & Liquid Cheatsheet

A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.

Running

Running a local server for testing purposes:

	import xlrd
	import sys

	if __name__ == '__main__':
	if len(sys.argv) != 2:
	print "Usage: git-xlsx-textconv file.xslx"

	excelFileName = sys.argv[1]

	xlFile = xlrd.open_workbook(excelFileName)

	[
	{
	"city": "New York",
	"growth_from_2000_to_2013": "4.8%",
	"latitude": 40.7127837,
	"longitude": -74.0059413,
	"population": "8405837",
	"rank": "1",
	"state": "New York"
	},

	/* bling.js */
	window.$ = document.querySelector.bind(document);
	window.$$ = document.querySelectorAll.bind(document);
	Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); };
	NodeList.prototype.__proto__ = Array.prototype;
	NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); };

	I'm really trying not to be rude but the number of recruiter spam I'm getting is really becoming irritating. For future reference:
	a) Don't email me an opportunity off the back of a key word search. Check out my cv or linkedin profile before forwarding opportunities. It really shows a complete lack of effort on your part
	b) I've dealt with a lot of recruiters in my time. A £500 referral fee in pathetic considering the potential fee your company receives on each placement.

	Going forward, I'll be telling my network of technical people about every recruiter/recruitment company which clearly isn't concerned about the level of service they provide and shows a distinct lack of effort when it comes to matching potential candidates to a role. As you know, the London tech scene is very similar to the game 'six degrees of kevin bacon' - word gets around.

	I hope this provides some insight and helps with future placements.

	Kind Regards

	# Ruby is our language as asciidoctor is a ruby gem.
	lang: ruby
	before_install:
	- sudo apt-get install pandoc
	- gem install asciidoctor
	script:
	- make
	after_success:
	- .travis/push.sh
	env:

	// === Arrays

	var [a, b] = [1, 2];
	console.log(a, b);
	//=> 1 2


	// Use from functions, only select from pattern
	var foo = () => [1, 2, 3];

	var delay = 250;
	var until = 'faux123';

	var a = new Array();
	$('button[class*=follow-btn]').each(function() {
	var attr = $(this).parent().attr('data-screen-name');
	if (attr != undefined) {
	if (attr == until) {
	return false;
	}