moenn

windows代理软件需要开启允许LAN连接

1. 安装 polipo

sudo apt install polipo

2. 配置 polipo

vim /etc/polipo/config
在文件中写入如下内容:

socksParentProxy = "localhost:1080"
socksProxyType = socks5

CatTail

var assert = require('assert')
var util = require('util')

function test (inherits) {
    function Fruit () {

    }
    Fruit.prototype.round = false
    Fruit.prototype.sweet = true
    Fruit.prototype.eat = function () {}

djcsdy

In the Unity editor:

1. Edit -> Project Settings -> Editor
2. In the inspector panel, set:
3. Version Control -> Mode: Visible Meta Files
4. Asset Serialization -> Mode: Force Text

“Visible Meta Files” causes Unity to place .meta files next to each of your assets. It’s important to check these files into version control because they contain the settings associated with those assets that you set in the Unity editor.

“Asset Serialization: Force Text” causes Unity to write its .meta and other files in a more-or-less human-readable text format, which makes it a lot easier to understand what has changed when you look at version control logs. Also it’s feasible to merge these text files by hand, whereas it’s not really possible to do that with Unity’s default binary file format.

ymjing

Powerline-patched Monaco for Windows and OSX

This font is manually patched with Fontforge. It includes the glyphs from DejaVu Sans Mono for Powerline.

I recommend DirectWrite-patched VIM builds. I'm using KaoriYa's build (http://www.kaoriya.net/software/vim/)

Usage

Add the following lines to your .vimrc/_vimrc:

laispace

git config --global https.proxy http://127.0.0.1:1080

git config --global https.proxy https://127.0.0.1:1080

git config --global --unset http.proxy

git config --global --unset https.proxy


npm config delete proxy

acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

chrislukkk

package Chapter5;

public class DecimalRepr {
    private static double ROUND_ERR = 0.0000000001;
    
    public static void printBinary(double realNum) {
	if(realNum >= 1 || realNum <= 0) return;
	StringBuilder repr = new StringBuilder();
	repr.append("0.");
	double m = 0.5;

davidzchen

// Sample file using the Google C++ coding standard.
//
// http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
//
// General rules:
//   - Indents are two spaces. No tabs should be used anywhere.
//   - Each line must be at most 80 characters long.
//   - Comments can be // or /* but // is most commonly used.
//   - File names should be lower_case.c or lower-case.c
//

mprymek

# This is an example of metaprogramming in the Elixir language.
# 
# We will define a domain specific language (DSL) for the definition
# of a service which is watched by several sensors.
# Each sensor watches some property/functionality of the service and
# returns the result of the check.
# 
# To determine if the service is functioning properly, we need functions
# to run all the sensors' code and gather the returned data.
# 

edokeh

//
//                       _oo0oo_
//                      o8888888o
//                      88" . "88
//                      (| -_- |)
//                      0\  =  /0
//                    ___/`---'\___
//                  .' \\|     |// '.
//                 / \\|||  :  |||// \
//                / _||||| -:- |||||- \