lacko lackofdream

The introduction to Reactive Programming you've been missing

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.

Noise: Unity editor has lots of temporary files that we don’t want git to track
Broken object references: Unity keeps track of objects created by using random GUIDs, and if they aren’t tracked using .meta files then there can be conflicts that really break your project
Unresolvable merge conflicts: files like scene files that are written in confusing languages (like YAML) that are supposed to be translations of Unity editor actions into code. Most likely, you cannot resolve using Git, and the only way to resolve merge conflicts is to open it in a text editor and resolve them manually while hoping you don't mess anything up because these files are confusing and not meant to be manipulated directly.
Large files: Sometimes assets are large and take up a lot of storage space


	import os
	import upyun
	from progressbar import *

	# http://stackoverflow.com/questions/1192978/python-get-relative-path-of-all-files-and-subfolders-in-a-directory
	myFolder = "/podcast/pod/podcasts/"
	os.chdir(myFolder)
	fileSet = set()

	int Kmp(const std::string& a, const std::string& b) {
	if (b.empty()) {
	return 0;
	}
	int n = (int)b.size();
	std::vector<int> p(n);
	if (n > 1) {
	p[1] = 0;
	}
	for (int i = 2, j = 0; i < n; i++) {