Sam Qiu samqiu

## .zshrc
gifify() {
  if [[ -n "$1" ]]; then
    if [[ $2 == '--good' ]]; then
      ffmpeg -i $1 -r 10 -vcodec png out-static-%05d.png
      time convert -verbose +dither -layers Optimize -resize 600x600\> out-static*.png  GIF:- | gifsicle --colors 128 --delay=5 --loop --optimize=3 --multifile - > $1.gif
      rm out-static*.png
    else
      ffmpeg -i $1 -s 600x400 -pix_fmt rgb24 -r 10 -f gif - | gifsicle --optimize=3 --delay=3 > $1.gif
    fi
  else

## StripeTutorialPage.html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta http-equiv="Content-type" content="text/html; charset=utf-8" />
  <title>Stripe Getting Started Form</title>

  <!-- The required Stripe lib -->
  <script type="text/javascript" src="https://js.stripe.com/v1/"></script>

  <!-- jQuery is used only for this example; it isn't required to use Stripe -->

## issues_with_modules.md

      
              1 file
            
          
              14 forks
            
          
              23 comments
            
          
              118 stars
            
          
                ryanb
                / issues_with_modules.md
            
            
              Created
              November 29, 2012 22:38
            
              
                Points on how modules can make code difficult to read.
              
          
    My issues with Modules

In researching topics for RailsCasts I often read code in Rails and other gems. This is a great exercise to do. Not only will you pick up some coding tips, but it can help you better understand what makes code readable.
A common practice to organize code in gems is to divide it into modules. When this is done extensively I find it becomes very difficult to read. Before I explain further, a quick detour on instance_eval.
You can find instance_eval used in many DSLs: from routes to state machines. Here's an example from Thinking Sphinx.
class Article &lt; ActiveRecord::Base

  
## gist:3888120

      
              1 file
            
          
              9 forks
            
          
              0 comments
            
          
              36 stars
            
          
                clintongormley
                / gist:3888120
            
            
              Created
              October 14, 2012 09:44
            
              
                Upgrading a running elasticsearch cluster
              
          
    Yesterday I upgraded our running elasticsearch cluster on a site which serves a few million search requests a day, with zero downtime. I've been asked to describe the process, hence this blogpost.
To make it more complicated, the cluster was running elasticsearch version 0.17.8 (released 6 Oct 2011) and I upgraded it to the latest 0.19.10. There have been 21 releases between those two versions, with a lot of functional changes, so I needed to be ready to roll back if necessary.
Our setup:


elasticsearch

We run elasticsearch on two biggish boxes: 16 cores plus 32GB of RAM. All indices have 1 replica, so all data is stored on both boxes (about 45GB of data). The primary data for our main indices is also stored in our database. We have a few other indices whose data is stored only in elasticsearch, but are updated once daily only. Finally, we store our sessions in elasticsearch, but active sessions are cached in memcached.

  
## README.markdown

      
              2 files
            
          
              20 forks
            
          
              20 comments
            
          
              59 stars
            
          
                greypants
                / README.markdown
            
            
              Last active
              October 17, 2023 05:49
                — forked from reagent/nav_link.rb
            
              
                RAILS 3: nav_link helper for adding 'selected' class to navigation elements
              
          
    UPDATE: It's a gem!

This helper has finally been moved into a gem called nav_lynx!
https://github.com/vigetlabs/nav_lynx
http://rubygems.org/gems/nav_lynx
Thanks to @brianjlandau and @reagent for getting that set up and tested!
Behold, the nav_link:


## history.txt
* Only the releases of the stable versions are listed in principle.  The releases of the unstable versions especially considered to be important are indicated as "not stable."
* The branches used as the source of each releases are specified, and the branching timing of them are also shown.  BTW, before subversionizing of the repository, the term called "trunk" was not used, but this list uses it in order to avoid confusion.
* In order to show a historical backdrop, big conferences (RubyKaigi, RubyConf and Euruko) are also listed.  About the venues of such conferences, general English notations are adopted, in my hope.
* ruby_1_8_7 branch was recut from v1_8_7 tag after the 1.8.7 release because of an accident.
* 1.2.1 release was canceled once, and the 2nd release called "repack" was performed.  Although there were other examples similar to this, since the re-releases were performed during the same day, it does not write clearly in particular.
* Since 1.0 was released with the date in large quantities, the mi

## 為什麼文科生也該用markdown寫作.md

      
              1 file
            
          
              2 forks
            
          
              2 comments
            
          
              10 stars
            
          
                illy
                / 為什麼文科生也該用markdown寫作.md
            
            
              Created
              June 21, 2012 04:36
            
              
                豆瓣預覽
              
          
    前陣子一直打算謝謝markdown寫作，拖到現在被這位老兄搶了先，很不錯的介紹文章：[为什么Markdown+R有较大概率成为科技写作主流？]（http://www.douban.com/note/220903450/）.所以我就不再重複了，此文打算用問答的形式介紹下markdown對於文科寫作的意義[^ft]。
###1. 什麼是markdown？
markdown是一種輕量化的標記語言。大家所熟知的標記語言還有latex，lyx， XML，HTML，這類文本的特點就是你在編輯時可以使用各種tag來控制文本的格式。話說回來，mac下的pages，M$的docx也都時XML文檔，只是你在編輯的時候，不需要加入tag，軟件本身替你增加tag了。
這類語言最大的好處就是在編輯時，你可以很大程度的減少格式對於文本的干擾。你想啊，打開一個word文檔，你調個文字大小，設置個 加粗，二號標題，再來個 斜體 什麼的,  時間大半過去了。而標記語言的最大優勢在於，你只要使用系統能夠識別的tag就可以非常方便地控制這些格式。比如markdown，你可以先使用系統默認的那些tag來寫作，等到最後輸出的時候，配置下css模版即可。
markdown是各種標記語言中的小兄弟，一來是因為它年輕，二來因為它非常輕量化。md是 John Gruber 和 Aaron Swartz 最初發明的，廣泛用於技術文檔的寫作。它的最大優勢在於人機皆可讀 （machine-readble, human-readble)。

  
## tmux-cheatsheet.markdown

      
              1 file
            
          
              3254 forks
            
          
              181 comments
            
          
              14306 stars
            
          
                MohamedAlaa
                / tmux-cheatsheet.markdown
            
            
              Last active
              May 3, 2024 19:09
            
              
                tmux shortcuts & cheatsheet
              
          
    tmux shortcuts & cheatsheet

start new:
tmux

start new with session name:
tmux new -s myname


## latency.markdown

      
              2 files
            
          
              742 forks
            
          
              49 comments
            
          
              4384 stars
            
          
                hellerbarde
                / latency.markdown
            
            
              Created
              May 31, 2012 13:16
                — forked from jboner/latency.txt
            
              
                Latency numbers every programmer should know
              
          
    Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs

  
## latency.txt
Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD
	gifify() {
	if [[ -n "$1" ]]; then
	if [[ $2 == '--good' ]]; then
	ffmpeg -i $1 -r 10 -vcodec png out-static-%05d.png
	time convert -verbose +dither -layers Optimize -resize 600x600\> out-static*.png GIF:- \| gifsicle --colors 128 --delay=5 --loop --optimize=3 --multifile - > $1.gif
	rm out-static*.png
	else
	ffmpeg -i $1 -s 600x400 -pix_fmt rgb24 -r 10 -f gif - \| gifsicle --optimize=3 --delay=3 > $1.gif
	fi
	else
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
	<title>Stripe Getting Started Form</title>

	<!-- The required Stripe lib -->
	<script type="text/javascript" src="https://js.stripe.com/v1/"></script>

	<!-- jQuery is used only for this example; it isn't required to use Stripe -->
	* Only the releases of the stable versions are listed in principle. The releases of the unstable versions especially considered to be important are indicated as "not stable."
	* The branches used as the source of each releases are specified, and the branching timing of them are also shown. BTW, before subversionizing of the repository, the term called "trunk" was not used, but this list uses it in order to avoid confusion.
	* In order to show a historical backdrop, big conferences (RubyKaigi, RubyConf and Euruko) are also listed. About the venues of such conferences, general English notations are adopted, in my hope.
	* ruby_1_8_7 branch was recut from v1_8_7 tag after the 1.8.7 release because of an accident.
	* 1.2.1 release was canceled once, and the 2nd release called "repack" was performed. Although there were other examples similar to this, since the re-releases were performed during the same day, it does not write clearly in particular.
	* Since 1.0 was released with the date in large quantities, the mi
	Latency Comparison Numbers (~2012)
	----------------------------------
	L1 cache reference 0.5 ns
	Branch mispredict 5 ns
	L2 cache reference 7 ns 14x L1 cache
	Mutex lock/unlock 25 ns
	Main memory reference 100 ns 20x L2 cache, 200x L1 cache
	Compress 1K bytes with Zippy 3,000 ns 3 us
	Send 1K bytes over 1 Gbps network 10,000 ns 10 us
	Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD