Arijit Das arijitAD

在 .zshrc 文件添加以下行：

bindkey "^[^[[D" backward-word  # bind ``option ←``
bindkey "^[^[[C" forward-word  # bind ``option →``

其中 ^[^[[D 是我运行 cat 后按 option + ← 的输出结果。

参考：http://stackoverflow.com/questions/12382499/looking-for-altleftarrowkey-solution-in-zsh

Competitive Programming Syllabus

Geometry

Graham Scan algorithm for Convex Hull O(n * log(n))
Online construction of 3-D convex hull in O(n^2)
Bentley Ottmann algorithm to list all intersection points of n line segments in O((n + I) * logn)
- Suggested Reading - http://softsurfer.com/Archive/algorithm_0108/algorithm_0108.htm
Rotating Calipers Technique
- Suggested Reading - http://cgm.cs.mcgill.ca/~orm/rotcal.html

Problems - Refer the article for a list of problems which can be solved using Rotating Calipers technique.

History Data Structures

For stateful applications, there are 5 different ways of managing the history of state:

No History - Living in the moment. - Examples: Any stateful application that doesn't discards all previous states upon mutation.
Ad Hoc Snapshotting - Allows restoration to manually saved snapshots. - Examples: Memento Pattern.
Singleton - Only remembers the previous snapshot, where undoing the undo is just another undo. - Examples: Xerox PARC Bravo.
1 Stack - Allows linear undo. - Examples: AtariWriter.
2 Stack - Allows linear undo and redo. - Examples: Browser History, Microsoft Word, Adobe Photoshop.

Install diff-so-fancy via their website (or just run npm install -g diff-so-fancy)
Add the following to your .gitconfig file:

[core]
  pager = diff-so-fancy | less --tabs=1,5 -R

I find that these colors work best with it, but it's up to you if you want to add them to your .gitconfig or not.

[color "diff"]
 meta = "yellow bold"

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Problems & Solutions for Interaction Between C and Go

At Vimeo, on the transcoding team, we work a lot with Go, and a lot with C, for various tasks such as media ingest. This means we use CGO quite extensively, and consequently, have run into bits that are perhaps not very well documented, if at all. Below is my effort to document some of the problems we've run into, and how we fixed or worked around them.

Many of these are obviously wrong in retrospect, but hindsight is 20/20, and these problems do exist in many codebases currently.

Some are definitely ugly, and I much welcome better solutions! Tweet me at @daemon404 if you have any, or have your own CGO story/tips, please! I'd love to learn of them.

Table of Contents

Example: Moving up to a few commits to another branch

Branch A has commits (X,Y) that also need to be in Branch B. The cherry-pick operations should be done in the same chronological order that the commits appear in Branch A.

cherry-pick does support a range of commits, but if you have merge commits in that range, it gets really complicated

git checkout branch-B
git cherry-pick X
git cherry-pick Y

	# GET VERSION
	npm -v (or --version)

	# GET HELP
	npm help
	npm

	# CREATE PACKAGE.JSON
	npm init
	npm init -y (or --yes)

	import os, filecmp

	codes = {200:'success',404:'file not found',400:'error',408:'timeout'}

	def compile(file,lang):
	if lang == 'java':
	class_file = file[:-4]+"class"
	elif lang == 'c':
	class_file = file[:-2]
	elif lang=='cpp':

	server {
	client_body_in_file_only clean;
	client_body_buffer_size 32K;

	client_max_body_size 300M;

	sendfile on;
	send_timeout 300s;
	# Port that the web server will listen on.
	#listen 80;