XC xchehub

some tools for diagrams in software documentation

Diagrams For Documentation

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.

I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!

\

REST/JSON is perfect match to fetch web data, and python requests module

Ex1: using command line tool curl and browser to access http://httpbin.org/get
Ex2: Install requests module and try to access http://httpbin.org/get in python interactive module, print r.json()
Ex3: Use below restapi.py as base to implement access data in script
Ex4: continue to access https://api.github.com via GET method

	## Ignore Visual Studio temporary files, build results, and
	## files generated by popular Visual Studio add-ons.

	# User-specific files
	*.suo
	*.user
	*.sln.docstates

	# Build results

	xxx,

	Thanks again for taking the time to speak with me and for sending me your information. I'm excited to tell you that we would like to move forward in the process!

	One of our coordinators will be emailing you within the next week from an @google.com domain with the date and time of your phone interview. In the meantime, I've included some preparation materials (below.)

	Please note this will be a technical interview that will last for approximately 45 minutes. Google takes an academic approach to the interviewing process. This means that we are interested in your thought process, your approach to problem solving as well as your coding abilities. You may be asked questions that relate to technical knowledge, algorithms, coding, performance, how to test solutions, and perhaps your interest in Google products. The best advice that I can give you is to treat the interview like a conversation, talk through the problems, and please feel free to ask the interviewer if you are not clear with any of the questio

	# Import files under folder name fawn
	# It is very important to include the option (full.names=TRUE). It it is not included
	# then you will get the error something like
	# "Error in file(file, "rt") : cannot open the connection In addition: Warning message:
	#In file(file, "rt") : cannot open file 'FAWN_2002.csv': No such file or directory

	mydata=ldply(list.files(path="data/fawn/",pattern="csv",full.names=TRUE),function(filename) {
	dum=read.csv(filename)
	dum$filename=filename
	return(dum)