Rong Hu hardproblems

Multiple SSH Keys settings for different github account

create different public key

create different ssh key according the article Mac Set-Up Git

$ ssh-keygen -t rsa -C "[email protected]"

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

EDIT from 2019: Hi folks. I wrote this gist for myself and some friends, and it seems like it's gotten posted somewhere that's generated some (ahem, heated) discussion. ~~The whitespace was correct when it was posted, and since then GitHub changed how it formats <pre> tags. Look at the raw text if you care about this. I'm sure someone could tell me how to fix it, but~~ (thank you @anzdaddy for suggesting a formatting workaround) honestly this is a random throwaway gist from 2015, and someone more knowledgable about this comparison should just write a proper blog post about it. If you comment here I'll hopefully see it and stick a link to it up here. Cheers. @oconnor663

Here's the canonical TOML example from the TOML README, and a YAML version of the same.

title = "TOML Example"

Preamble

On OS/X Sierra, after recently running a brew update I started receiving the error message Sorry, you can't use byebug without Readline when trying to run some rake tasks in my ruby project folder. I observed this in projects and gems that include byebug or pry in their Gemfile or gem.spec. I've found in my googling that many begin encountering this error message after running a brew update but there are other triggering conditions as well.

>> rake aws:show_config
WARN: Unresolved specs during Gem::Specification.reset:
      mime-types (>= 0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
 Sorry, you can't use byebug without Readline. To solve this, you need to

📂 Minimize allocations in Go

A collection of tips for when you need to minimize the number of allocations in your Go programs.

Use the go profiler to identify which parts of your program are responsible for most allocations.

⚠️ Never apply these tricks blindly (i.e. without measuring the actual performance benefit/impact). Most of these tricks cause a tradeoff between reducing memory allocations and other aspects (including e.g. higher peak memory usage, higher CPU usage, lower maintainability, higher probability of introducing subtle bugs). Only apply these tricks if the tradeoff in every specfic case is globally positive.

	require 'rubygems'
	require 'mechanize'

	FIRST_NAME = 'FIRST_NAME'
	LAST_NAME = 'LAST_NAME'
	PHONE = 'PHONE'
	EMAIL = '[email protected]'

	PARTY_SIZE = 2
	SCHEDULE_RANGE = { :start_time => '19:00', :end_time => '20:30' }

	package samples

	import org.junit.runner.RunWith
	import org.scalatest.junit.JUnitRunner
	import org.scalatest._
	import org.springframework.beans.factory.annotation.Autowired
	import org.springframework.context.annotation._
	import org.springframework.stereotype.Service
	import org.springframework.test.context.support.AnnotationConfigContextLoader
	import org.springframework.test.context.{ActiveProfiles, ContextConfiguration, TestContextManager}

	#!/usr/bin/env ruby

	require 'erb'
	require 'json'
	require 'optparse'
	require 'ostruct'

	class ERBContext
	def initialize(hash)
	raise ArgumentError, 'hash must be a Hash object' unless hash.is_a?(::Hash)

	import org.scalatest.{BeforeAndAfterAll, Suite}
	import org.springframework.core.annotation.{AnnotatedElementUtils, AnnotationAttributes}
	import org.springframework.test.annotation.DirtiesContext
	import org.springframework.test.context.{TestContext, TestContextManager}
	import org.springframework.test.context.support.DirtiesContextTestExecutionListener
	import org.springframework.util.Assert

	/**
	* Manages Spring test contexts via a TestContextManager.
	*