jexchan

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 "your_email@youremail.com"

peterk87

/*bitbucket.org dark css theme*/

body, aside {
	background: #222 !important;
	background-color: #222 !important;
	color: #bbb !important;
}
h1, h2, h3, h4, h5, span {
	background-color: transparent !important;
	color: #FFC963 !important;

rtt

Tinder API documentation

Note: this was written in April/May 2014 and the API may has definitely changed since. I have nothing to do with Tinder, nor its API, and I do not offer any support for anything you may build on top of this. Proceed with caution

http://rsty.org/

I've sniffed most of the Tinder API to see how it works. You can use this to create bots (etc) very trivially. Some example python bot code is here -> https://gist.github.com/rtt/5a2e0cfa638c938cca59 (horribly quick and dirty, you've been warned!)

orendzi

/************************* SETTINGS *****************************/
p.s. git config can be changed in file .gitconfig or in console:

CONFIGURE GIT (optional)
1. Set your name
$ git config --global user.name <YOUR NAME>

2. Set your email
$ git config --global user.email <YOUR EMAIL ADDRESS>

aalvesjr

Neste primeiro módulo, vamos analisar alguns comandos do Bash, os mais conhecidos e usados, juntamente com algumas de suas opções. A maioria dos comandos permitem o uso de inúmeras opções, não sendo possível abordar todos elas neste texto.

Antes de iniciarmos, vale lembrar que os manuais de todos os comandos podem ser lidos usando o comando man nome_do_comando, por exemplo:

$ man echo A maioria dos comandos também têm a opção -h, ou –help, que lista os parâmetros aceitos pelo programa.

Os comandos estão ordenados alfabeticamente, sem levar em consideração relevância ou complexidade de utilização.

Sumário

parmentf

Inspired by dannyfritz/commit-message-emoji

See also gitmoji.

Commit type	Emoji
Initial commit	🎉 :tada:
Version tag	🔖 :bookmark:
New feature	✨ :sparkles:
Bugfix	🐛 :bug:

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

SynCap

<# 
Note: Eliminate `-WhatIf` parameter to get action be actually done 
Note: PS with version prior to 4.0 can't delete non-empty folders
#>

Get-ChildItem -Path "." -Include "node_modules" -Recurse -Directory | Remove-Item -Recurse -Force -WhatIf

jkrems

Modules - History & Future

History

• Early work by Ihab Awad (Google) and Kris Kowal (FastSoft)
  • https://twitter.com/kriskowal/status/943547614158450688
  • Hermetic eval presentation: https://docs.google.com/presentation/d/1KlPxgocvzpTq44KTF4xZ6TnzGRsy628hP5he7bXVB3I/edit#slide=id.i0
• 2009-09: 2nd draft of module strawman, still very close to "closures as modules", export x = 42
  • https://esdiscuss.org/topic/hermetic-evaluation-modules-strawman

• https://docs.google.com/document/u/1/pub?id=1hNv1SHh_v_6nD1QBd6pySUJ2U5roAELzW5cqD2tt_WM